Documentation

Site Settings

A site in SleekCMS is the container for one content surface — one set of models, one set of content records, one set of templates, and one deployment target. Site settings cover everything that controls how the site behaves at the administrative level: builder configuration, image processing, localization, team membership, clone tokens, and site lifecycle.

This page orients you around the two settings screens — Site Configuration and Site Members — and what belongs where.

Site Configuration

The configuration screen controls the technical behavior of the site. This is where you toggle the site builder, set the image processing backend, configure localization, choose key-naming conventions, and manage the site's identity and lifecycle (display name, clone tokens, deletion).

These settings affect all content and rendering on the site. They are intended for admins — editors do not see this screen.

→ Site Configuration

Site Members

The members screen controls who has access to the site and what they can do. SleekCMS uses a two-role model — admin and editor — with optional fine-grained access controls on individual editors for restricting models, languages, deploy targets, and publish triggers.

This is where you invite teammates, change roles, remove members, and configure per-editor access scopes.

→ Site Members

Site vs. Organization

Settings divide cleanly between two levels:

  • Site settings (this section) affect a single content site — its models, content, templates, deployment, and team.
  • Organization settings (Organization Management) affect the org as a whole — billing, the list of sites in the org, and org-wide membership.

Members are managed at both levels. An organization member has access to the org dashboard and can be granted access to specific sites. A site member has access scoped to one site only.

→ Organization Management

What's Next