Organization Management
An organization is the top-level container in SleekCMS. Every site belongs to one organization. Members, billing, and the list of sites all sit at the org level. This is your workspace boundary.
The Organization section of the CMS is where you manage the org as a whole: the sites that belong to it, the people who can access those sites, the subscription that pays for them, and the templates available for cloning new sites.
What Lives at the Org Level
Four things are managed at the organization level rather than at the site level:
Sites — The list of content sites your org owns. From here you create new sites (blank or cloned from a template), open existing sites, and configure site-level access for org members.
Members — The people who can access the org. Org members can be granted access to any number of sites within the org. Roles at the org level are independent of roles at the site level — an org admin can see the org dashboard and billing, while a site admin only manages a single site.
Subscription — Billing, plan, and seat management. The subscription determines how many sites the org can hold, how many members can be invited, and what features are enabled. Owners manage the subscription; admins and editors do not see this screen.
Templates — Cloneable starter sites available to the org. The template gallery is shared across the org and includes both the public template library and any custom templates your team has saved as clonable sites.
Org vs. Site
The split between org-level and site-level settings is intentional:
- Org owns: billing, the list of sites, org-wide membership, available templates.
- Site owns: content models, content records, view templates, deployment, site-specific membership, and site configuration.
A site's settings page does not show billing. The organization's dashboard does not show content models. This keeps each surface focused — content teams work inside a single site without seeing billing they don't manage, and org admins manage subscriptions and seats without scrolling past content.
Multiple Sites in One Org
An organization can hold any number of sites — limited only by your subscription plan. Common patterns:
- Agency — One org, many sites, one site per client.
- Multi-brand company — One org, one site per brand, each with its own models and content.
- Staging and production — Use environments within a single site rather than separate sites. Sites are independent content containers, not deployment environments.
→ Sites — Detailed management of the sites in your org.
What's Next
- Sites — Creating, opening, and managing the sites in your organization.
- Members — Inviting teammates and configuring org-level access.
- Subscription — Billing, plans, and seat management.
- Templates — Cloning sites from templates and sharing your own.
- Site Settings — Settings scoped to a single site (config and members).