Roles and billing seats
Owner through Viewer, and what “Cover seat” means.
Roles (Owner, Editor, Contributor, Viewer) control what someone can do in a project. Billing seats control your AI credit allowance and feature access. The two are independent — a seat does not grant a role, and a role does not require a seat.
Roles on projects you own vs. projects you join
When you create a project you are automatically its Owner. On projects someone else owns and invites you to, they choose your role — you can be assigned Editor, Contributor, or Viewer regardless of your plan or whether your seat is covered. There is no plan requirement to hold a particular role on someone else's project.
Cover seat
"Cover seat" assigns one of your purchased collaborator seats to a specific person. It lifts their AI credit allowance and Pro/Business feature access to match your plan. It does not change their project role — role is set separately on the project's People page. Remove seat when you want to free that slot for someone else.
Roles (summary)
- Owner: Full control including ownership semantics.
- Editor: Same project management powers as owners except the owner designation.
- Contributor: Work on assigned actions and use allowed collaboration features without full admin access.
- Viewer: Read-focused access.
The project People page lists the full role descriptions and matches what invitees should expect.
Permissions matrix (quick reference)
| Capability | Owner | Editor | Contributor | Viewer |
|---|---|---|---|---|
| View project content | Yes | Yes | Yes | Yes |
| Create/edit actions | Yes | Yes | Assigned-work focused | No |
| Manage project people and roles | Yes | Yes | No | No |
| Configure project integrations | Yes | Yes | No | No |
| Project configuration/admin behavior | Full | Most | Limited | Read-only |
To invite people and set roles, open the project's People page.
Removing someone from a project
When you remove a person from a project they immediately lose access to it. Any open actions they were responsible for are automatically unassigned, and a note is added to each affected action explaining the change. Completed (Done) actions are left untouched.
When a covered person is removed from a project or their seat is unassigned, that seat slot becomes available again. Their role on the project is a separate setting and is not affected by seat removal.