Documentation

Organization and Sites

An organization can hold any number of sites — agency clients, multi-brand portfolios, separate product surfaces, staging laboratories. Each site is an independent content container with its own models, content, templates, members, and deployment. The org gives them shared billing, shared org-level membership, and a single dashboard to switch between them.

This page covers what a site is, how to create and switch between sites, and how site-level access fits with org-level access.

What a Site Is

A site is the unit of content in SleekCMS. Inside a site, you have:

  • Models — page, entry, and block schemas specific to that site.
  • Content — page records, entry records, and inline block data.
  • Templates and assets — the site builder's EJS templates, CSS, JS, and static files.
  • Members — site-scoped admins and editors (in addition to org-level members).
  • Deploy targets — Netlify, surge.sh, or download configurations specific to this site.
  • Environments — content version aliases for staged publishing.

Two sites under the same org are fully independent. They don't share models, content, or templates. The org is just a logical and billing boundary.

Creating a Site

From the org's Sites screen, the Create Site button starts a new site. Two paths:

From a template — Choose a template from the gallery (or paste a clone token for a private template). The new site is created as an independent copy of the template — all of its models, templates, content, and assets are duplicated. Subsequent changes to the original template don't propagate.

Blank — Create an empty site. No models, no content, no templates. You start from scratch with the content modeler.

Either path produces a fully independent site that's yours to edit.

→ Templates → Getting Started

Switching Between Sites

The site switcher in the SleekCMS interface lists every site in your current org that you have access to. Switching loads that site's models, content, builder, and members — the URL changes to include the site's slug, and the page reloads with the new site's data.

If you're a member of multiple orgs, the org switcher is one level up. Most users only see one org; agencies and contractors with access to multiple orgs see them all.

Site Membership vs. Org Membership

Membership is layered. The two layers are independent:

Org membership (Members) determines who has access to the org as a whole — the dashboard, the list of sites, the subscription, and the org members screen.

Site membership (Site Members) determines who has access to a specific site's content, models, and builder.

An org member can be added to any number of sites within that org. Conversely, a site member must be an org member first.

Different roles can apply at each level. A user might be an org admin but only an editor on one specific site, or an org member with no site access at all (until they're invited to a specific site).

For most teams the layering is invisible — everyone is an org member with access to every site. The split matters when you need finer control: agencies who want clients to see only their own site, contractors who should only access one site, or teams where the billing owner shouldn't have edit access to every project.

→ Members → Site Members

Site Limits and Subscription

The number of sites an org can hold is tied to its subscription plan. Reaching the limit prompts you to upgrade the plan or purchase additional site slots when you try to create a new site.

Deleting a site frees up a slot. Cloned sites count the same as built-from-scratch sites — every site, regardless of origin, occupies one slot in the plan.

→ Subscription

Site Slugs and URLs

Each site has a slug — a short identifier that appears in the SleekCMS admin URL when you're working in that site (e.g., /<site-slug>/content, /<site-slug>/builder). The slug is independent of the site's deployed URL — your deployed site can be at any custom domain you've configured at the deploy layer.

Slugs are stable once assigned. If you need to rename a site for organizational reasons, change the display name in Site Configuration; the slug stays the same.

Common Setups

Single site — Most orgs start (and stay) with a single site. The org wrapper is mostly invisible — billing, members, that's it.

Multi-brand — One org per company, one site per brand. Each brand has its own models, content team, and deployed domain. Shared billing simplifies vendor management.

Agency — One org per agency, one site per client. Each client site is independent; the agency org sees them all. Clients can be granted site-level membership to their own site only (not the others).

Staging vs. production — Use a single site with multiple environments, not separate sites. Sites are independent content containers; staging and production are versioning concerns within a single site.

What's Next