Beta . Ortha CMS is in public beta. Every plan is free until it ends.
Get started
Menu

Governance · 15 / 23

Workspaces

Separate brands, clients or markets in one installation, each with its own members and its own content types.

Home Workspace Content Collections43
ArticlesAuthorsCategoriesEvents
ProductsCollectionsLookbooks
Tools Media Library Insights

SWITCH WORKSPACE

New workspace
SettingsGeneral Save changes
Settings General Content types43 Members53 Publishing rules Danger zone
General

How this workspace is named and shown, and whether other workspaces may use its records.

Identity Shown in the sidebar, the switcher and on every card.
Avatar color
N S
Name
NewsroomStorefront

A short, recognizable name for this workspace.

Description
Daily news and long reads from the city desk.The product catalogue behind shop.example.
Address and API Fixed when the workspace was created.
URL slug
newsroomstorefront
Workspace ID
3c1e5a0b-7d2f-…8f40c2e1-19aa-…

Identifies this workspace to the API. Send it as the X-Workspace-Id header when a token covers more than one workspace.

How it works

  1. 01

    Create a workspace with a name, a slug and a colour.

  2. 02

    Add members, and grant it the content types it may use.

  3. 03

    Switch between workspaces from the sidebar.

Members
Per workspace
Roles
Global, not per workspace
API
X-Workspace-Id header

In depth · For agencies and multi-brand teams

One installation, many workspaces

Run every brand or client from one deployment, each with its own content, members and dashboard.

Membership and permission both have to pass

Membership decides where you may act; your role decides what you may do. A non-member gets a 403 and never learns the workspace exists, so the switcher cannot be used to list your clients.

Each workspace gets its own content types

A workspace is granted the content types that exist inside it, and every query is scoped to it. A client granted articles and authors has no route to another client’s product catalogue.

Under the hood

An API token is granted specific workspaces too, so a client’s front end fetches its own content and nothing else.

One installation holding three workspaces, each granted a different set of content types.

Bell & Co has no route to a recipe.

Separate per workspace

  • Entries, of every content type
  • Which content types exist
  • The media library and its folders
  • Members
  • The insights dashboard
  • API token grants
  • Assistant conversations

Good to know

No workspace owner
Any member holding workspaces:update can add or remove members.
The last member stays
Removing the last member is refused, so a workspace is never left unreachable.
Archive before you delete
Archiving is reversible; a workspace that still holds records refuses to be deleted.
The audit log spans all
It covers every workspace, and only an administrator reads it.

Questions

How many workspaces can I have?

Unlimited during the beta. After 1.0, three on Community and unlimited on a plan.

Can a client see only their workspace?

Yes — add them to that workspace and no others. They will not see the rest exist.

Can brands share one media library?

No. Media is scoped to a workspace, so reusing an asset across two means uploading it twice.

Full reference in the docs