For: everyone. Nothing here needs a special role — the other article in this section is about managing a workspace, this one is about being in one.
A workspace is a container, and it is a strict one: every playbook, persona, file and chat belongs to exactly one. Nothing is shared between workspaces, and nothing moves between them by itself.
Why you may be in several
Teams split workspaces when the contents should genuinely not mix — one per client, one per department, or one that is being tried out before anyone commits. Each has its own members, its own AI provider keys and its own billing, which is usually the actual reason there is more than one.
You switch between them in the sidebar. ⚠️ Switching changes everything at once: a different set of playbooks, different personas, different files, different colleagues.
The practical consequence, and it is the common one
“I cannot find my playbook” is most often “I am in the other workspace.” Before assuming something was deleted or that your access was taken away, check the workspace name at the top of the sidebar.
This bites hardest outside the webapp. The browser extension follows one workspace at a time, and an MCP connection is created against one workspace — so a tool can be pointed somewhere other than the tab you are looking at. See My playbook does not appear where I expected it if that is where you are.
What your colleagues see, and what they do not
Worth knowing plainly, because people guess at this and usually guess wrong.
Playbooks, personas and files belong to the workspace, not to the person who made them — unless they carry a Restricted or Only me badge, which names who may open them.
“Only me” means only that person — not editors, and not admins either. A promise with an exception for management would not be a promise.
A chat is private to you until you share it with the workspace. Sharing is a deliberate act, and a shared conversation is how “how did you get that result” gets an answer that is not a screenshot.
Your MCP connection is yours alone. It answers with what you may see, which is exactly why you should never use a colleague's.
If you leave, or are removed
Anything you wrote stays in the workspace. Custody passes to the longest-standing admin — including anything you had set to “Only me”, which would otherwise be unreachable for everyone forever. That is custody, not authorship: the work continues to exist for the team that paid for it.
Your MCP connections leave with you, because they belong to you rather than to the workspace.
⚠️ So if you are handing over and something private still matters to somebody, pass it on before you go. Custody makes it reachable again, but it lands with an admin — who may not be the person who actually needed it.
Can I create one myself?
Creating and configuring workspaces is an admin's job, as is inviting people into them. If you need one — for a new client, say — ask an admin; it takes them a minute. What you can always do, whatever your role, is work in every workspace you have been added to.
Updated 27 September 2026 · Article version 1