Roles and what each can see
Project Admin, Editor and Viewer — what each can actually do, why a role does not follow you between projects, and why a missing button is usually correct.
Overview
Three roles, and the distinctions between them are concrete rather than abstract. The most useful thing to know is which controls each role actually gets — because when someone reports that a button has disappeared, the answer is usually that the access model is working.
What you'll learn
What each of the three roles can do
The practical difference between Admin and Editor
Why your role does not follow you between projects
The roles
Project Admin edits project data and manages membership.
Project Editor edits project data, but cannot manage membership.
Project Viewer is read-only.
What that means in practice
Add a member | Create a company | Launch a process | |
|---|---|---|---|
Project Admin | Yes | Yes | Yes |
Project Editor | No | Yes | Yes |
Project Viewer | No | No | No |
So the practical difference between Admin and Editor is membership. An Editor can do the work of a subscription process — create companies, launch KYC and subscription processes — but cannot decide who else has access.
A Viewer can look, and nothing more. Note that the controls are absent, not disabled: the buttons are not greyed out, they are not there.
That detail matters for diagnosis. Someone saying "the create button has gone" is usually describing correct behaviour for their role, not a fault.
The rule people get wrong
A project role does not follow you between projects. Roles are scoped to the specific project. The same person can be an Editor on one project and a Viewer on another, and that is normal rather than a misconfiguration.
So there is no account-wide level to check. To answer "what can this person do?", you have to ask it about a particular project.
Why it is built this way
An LBO involves people whose involvement differs per deal — an analyst staffed on one build-up and not another, an adviser who should see one project only. Per-project roles make that expressible. A single account-wide permission level could not.
Practical guidance
Default to Editor for deal-team members doing the work. Admin is for those who also manage access.
Use Viewer deliberately. It is genuinely read-only, and useful for people who need visibility without the ability to change anything.
Check the role, not the person, when someone says a control is missing.
Related
A1.2 — How Kapitable is organised · where roles sit in the model
A2.3 — Inviting your team · granting these roles
A2.6 — Access control in practice · reasoning about visibility across companies and processes
