Team Roles & Permissions

Roles control what each member can see and do in your workspace. Every member has one of three roles: Owner, Admin, or Member.

Owner

The Owner is the workspace creator. Owners have the same permissions as Admins and cannot be removed from the workspace. In the API, the Owner appears with the admin role.

There is no “transfer ownership” button in workspace settings. Ownership moves in exactly two situations: when the owner deletes their account and hands each workspace they own to an existing member or to someone invited by email (see Account Settings), and when support moves it for you.

Admin

Admins have full control over the workspace. They can create, edit, publish, and delete any document or project. They can also invite and remove members, change roles, modify workspace settings, manage integrations, configure the AI provider and webhooks, and access billing.

Member

Members have read-only access by default. They can read every project in the workspace and create new projects, but they can’t edit documents, manage the team, or reach workspace settings.

Drafts included. A draft is private to the workspace, not to its editors: every Member sees drafts in the tree, can open them, and finds them in search and Ask AI with Include drafts on. Only public readers never see drafts.

Members can create Integration Tokens too, and see and revoke only the tokens they created. Admins see and revoke every token in the workspace.

To give a Member editing access on a specific project, use Project Collaborators.

Permission matrix

Action	Owner	Admin	Member
View published docs	✅	✅	✅
View draft docs	✅	✅	✅
Create documents	✅	✅	❌
Edit documents	✅	✅	❌
Delete documents	✅	✅	❌
Publish documents	✅	✅	❌
Create projects	✅	✅	✅
Delete projects	✅	✅	❌
Invite members	✅	✅	❌
Remove members	✅	✅	❌
Change roles	✅	✅	❌
Workspace settings	✅	✅	❌
Integration tokens	✅ all	✅ all	Own only
Webhooks	✅	✅	❌
Billing	✅	✅	❌

Note: This matrix covers workspace-wide rights. A Member who creates a project becomes its Admin, and project collaborators can be granted Write, Write and Delete, or Admin on individual projects.

Assigning roles

Start new members as Members and use Project Collaborators to grant editing rights on specific projects. Reserve Admin for people who actively manage the workspace — inviting members, configuring settings, or handling billing.

Having at least two Admins is a good idea. If one is unavailable, the other keeps things running.

What’s next?

Project Collaborators — Give Members editing access on specific projects.

Invitations — Send invitations and manage pending ones.