Workspace
Organisations and workspaces
How your company is structured in cmdk, and what lives at each level.
Organisation
The organisation is your company. It has a name and a URL slug, members, and organisation-wide secrets. Its settings decide who may create workspaces: Admins only or Any member. Deleting an organisation asks you to type its name.
Open it from the workspace switcher at the top of the sidebar, or with Organisation in the ⌘K palette.
Workspace
A workspace is where a team works. Everything you use day to day belongs to one: chats, agents, channels, automations, skills, tools, knowledge, connected apps, API keys, messaging doors and the credits meter.
Workspace settings has these tabs:
| Tab | What it holds |
|---|---|
| General | Image, name, slug, default language, the workspace ID, and delete. |
| Members | Who is in the workspace, their role, invitations by email, and access requests. |
| Messaging & API | Slack, WhatsApp, Telegram, the MCP server and API keys. See Connect. |
| Roles | Named roles with per-area permissions. Owners only. See Members and roles. |
| Secrets | Named values such as API_KEY that tools and scripts can use without the value appearing in a prompt. Owners only. |
One workspace or several
Use one workspace when the team shares context. Use several when work must stay apart: different clients, different departments, or data that some members must not see. Connections, knowledge and credits do not cross workspaces.
Switching
The switcher at the top of the sidebar lists your workspaces and organisations. Creating a new one happens from the same menu, if your organisation allows it.
Secrets at two levels
Organisation secrets are available to every workspace; workspace secrets to that workspace only. The organisation Secrets tab is visible to admins.