Workspaces

What is a workspace

A workspace is the primary isolation unit in Cmssy. Everything you create — pages, blocks, forms, media, custom data models, themes, API tokens, members, roles — is scoped to a single workspace. Different workspaces never share data.

A single user account can belong to multiple workspaces at once, with different roles in each. You switch between them from the workspace selector.

Creating a workspace

1. Open the workspace selector (top of the sidebar) and click Create Workspace.
2. Fill in:
   • Name — the human-readable name of your workspace.
   • Slug — auto-generated from the name (lowercase, hyphen-separated). Editable before creation. The slug is an admin-side identifier for the workspace; your public site is your own Next.js deploy that pulls this workspace's content via the delivery API/SDK.
3. Click Create. The new workspace becomes active immediately and you're redirected to its dashboard.

Once created, the slug is locked. The name can be changed later in Settings, but the slug cannot. Choose carefully.

Reserved slugs

About 60 slugs are reserved for infrastructure and auth routes (api, www, admin, login, workspace, and similar). If you try to use one, the create form shows an error. Pick something unique to your brand.

Switching between workspaces

The workspace selector (header dropdown) lists every workspace you're an active member of. Clicking another workspace reloads the page to ensure a clean state — cached data from the previous workspace is never carried over.

Pending invitations don't appear in the switcher. Accept them first (link in the invitation email) and they show up as normal workspaces.

Plans and limits

Plans, limits and billing are managed at the organization level, not per workspace. A workspace belongs to an organization, and usage - pages, media storage, AI tokens and more - is pooled across all of the organization's workspaces and enforced against the organization's plan.

Adding a workspace doesn't add a separate quota: every workspace draws from one shared organization total. See Pricing for current plans and costs.

Ownership

Ownership lives at the organization level, not the workspace level. A workspace belongs to an organization, and that organization has exactly one owner. The org owner has unconditional access to every workspace the organization owns, regardless of role configuration - it is the only permission bypass. Within a workspace, everything else is governed by roles.

Transferring ownership

Ownership transfers at the organization level: the current org owner hands the organization - and with it the bypass over every workspace it owns - to another active member. You cannot transfer to yourself, and the target must already be an active member. The change is immediate.

Members and roles

Workspaces are collaborative. You invite teammates by email and assign them a role (Owner or a custom role you define). Members can be active, pending (invited, not yet accepted), or suspended.

Full details, including the role permission matrix: Members & Roles.

Deleting a workspace

Settings → General → Delete workspace. Only the owner can perform this action.

Deletion is immediate and permanent — there is no grace period, no soft delete, no undo. All of the following are destroyed:

• Pages, page drafts, page types
• Blocks (workspace-specific + templates)
• Media assets and uploaded files
• Forms and all form submissions
• Custom data models and records
• Site configuration and theme
• AI provider configuration
• Members and roles

Export or back up anything you want to keep before confirming.