Who can do what
Five grantable roles form one ladder; site membership, per-node permissions and API key scopes are the other three things that narrow what a request may do.
Four mechanisms decide what a request may do, and they layer rather than compete: a role sets the floor, membership decides which sites it applies to, a per-document grant narrows one page, and a key's scope narrows a request below even that.
Everything reduces to one floor on one ladder
role and the role ladder
Five roles can be given to an account — super admin, site admin, editor, author, reader — in one strict order. Every "can this role do X" check reduces to a minimum-role floor on it: reading content needs reader, writing needs author, publishing needs editor, deleting needs site admin, and roughly a dozen admin surfaces sit at site admin too. There's no per-capability toggle for a site admin to configure.
A sixth name, deny, sits below reader at level zero, but nothing hands it out: the admin keeps it off the list of assignable roles, and a per-document permission row can't carry it either, because those rows only ever grant. It exists so a check has a way to say "nothing" — which is what an API key resolves to when none of its scopes are recognized.
A role isn't scoped to one site by itself, and a change to it reaches a signed-in user only once their access token refreshes — see Managing users, roles and site access. For the floor-by-floor breakdown see Roles and the capability matrix, and for who moves content between statuses without review, Bypassing the queue: who can transition directly.
A group is somewhere to be targeted from, not a rank
The ladder is site-wide. The other three mechanisms all narrow it, starting with the one that looks most like a rank and isn't.
group
A named bucket of users, consumed in exactly two places in the whole platform: as the target of a content-level permission grant, and as the owner of one step in a multi-approver approval chain. It carries no role of its own and no site scope, and it can only ever add what a grant targets it with — never take away what a member's role already gives them. See Managing groups, and Reviewing and approving submissions for its second job.
The first grant is what closes a document
content permission (per-node ACL)
An additive grant — one user or one group, plus a single action — attached to one document. With zero grant rows a document stays open to anyone whose role already covers that action; adding the first grant is what switches that one document from open-by-role to closed-by-default for everyone else. A grant can hold back an author or an editor, never a site admin or super admin, and a mutation grant does nothing without a read grant beside it. See Content-level permission overrides.
A key's scopes are a ceiling, never a grant
API key scope
Each scope names the highest role it allows — read caps at reader, write at author, publish at editor, admin and developer both at site admin — and every request runs as whichever is lower: that ceiling, or the key owner's own role. Combining scopes takes the highest ceiling, not the sum, so a key scoped read, write and publish still ceilings at editor, one rung below what deleting content needs. No scope reaches super admin, and an empty or unrecognized scope set resolves to deny. See Authenticating an external caller for the wire contract, and API keys: scopes are a role ceiling for an agent working through the developer server.