For: admins. Only admins can invite people or change roles. Editors and members can read this to find out what they have.
Inviting is in Settings → Team. Add someone, pick their role, and they appear in the list once they accept.
The three roles
Admin — everything. Invites and removes people, changes roles, manages the plan and billing, manages the workspace's AI provider keys, and creates and edits playbooks and personas.
Editor — the building role. Creates and edits playbooks and personas, manages the workspace's AI provider keys, and reaches the general workspace settings. Cannot manage the team and cannot touch the plan or billing.
Member — the using role. Uses every playbook and persona they have access to, and creates their own MCP connection for their own tools. Cannot create or edit playbooks, cannot manage the team, and cannot see or change the workspace's provider keys or settings.
⚠️ The role is called member, not “user”. If you find an older instruction anywhere calling it a user, that text predates the current product.
What a role does NOT give you
This is the part that catches people out. No role grants access to a particular playbook. A playbook set to “Only me” is visible to its creator and to nobody else — not to editors, and not to admins. A restricted one is visible to its creator plus the people and groups named on it.
Being an admin means you run the workspace. It does not mean you read everything in it, and that is deliberate: “Only me” is a promise to one person, and a promise with an exception for management is not a promise.
How many people you can add
Each plan includes a number of seats, and they differ substantially between plans. Your current limit and how many are used are shown in Settings, which is the number to trust — plan contents change, and an article that repeats them will be wrong before it is old.
Choosing a role
Start people as members and promote on request. The useful question is not how much someone should be trusted but whether they will be writing playbooks: an editor who never writes one gained nothing, and a member who needs to write one will say so within a week.
Keep more than one admin. A workspace with a single admin has a single point of failure for billing, invitations and keys.
When somebody leaves
Remove them in Settings → Team. Two things happen automatically, and both are worth knowing about:
Their playbooks stay. Custody passes to the longest-standing admin still in the workspace — including their private ones, which would otherwise become unreachable for everyone forever. That is custody, not authorship.
Their MCP connections are removed. A connection belongs to one person, so it leaves with them. Anyone who was using that person's connection string — which they should not have been — loses access at the same moment.
It is worth telling a departing colleague to hand over anything set to “Only me” before they go. Custody makes it reachable again, but only an admin ends up holding it, which may not be the person who needs it.
Updated 27 September 2026 · Article version 1