Skip to content

Roles and the capability matrix

Six roles form one strict ladder, and every capability — content actions and every admin surface alike — reduces to a minimum-role floor on it.

Six roles form one strict ladder — super admin, site admin, editor, author, reader, and deny, from most to least privileged — and every "can this role do X" check in Kywi reduces to a minimum-role floor on that ladder. There's no per-capability toggle a site admin configures anywhere; a role either clears the floor for an action or it doesn't.

The capability matrix

The minimum role each action needs, generated from the same capability catalog and the same check the server enforces on every request — not a hand-maintained table that can drift from what actually runs.
NameTypeDefaultDescription
Read contentreader—
View the site tree, layout and existing content.
Write contentauthor—
Create and edit content — draft it, not publish it.
Publish contenteditorinto published only
Carry a draft through pending and approved into published. Nothing in the editor ladder can move a page back out of published — see the callout below.
Reverse a published pagesite admin—
Unpublish, archive, or otherwise move a page out of published. The editor ladder has no exit from published at all, regardless of what the admin shows on screen.
Delete contentsite admin—
Permanently remove a content record.
Users, groups and rolessite admin—
Invite a user, deactivate one, or change someone's role or group membership.
Content-permission overridessite admin—
Grant or revoke a document-level permission override — even when the access it hands out only needs author or editor.
Content types, media, webhooks, plugins, settings, API keyssite admin—
Roughly a dozen other admin surfaces all sit at this same floor.
Create or delete a sitesuper adminthe one action above site admin
The only capability the ladder reserves above site admin.
An API key's effective rolecapped, never super adminlower of owner's role and scope ceiling
A key's read scope caps at reader, write at author, publish at editor, and admin/developer at site admin — a key can only narrow its owner's role, never widen it.

When a role change takes effect

A user's role travels inside their access token rather than being looked up fresh on every request, and that token is short-lived. Change someone's role and it reaches them the next time their token refreshes — within minutes, in the ordinary course of using the admin, but not the instant you save the change. If a role change needs to apply right now, have that person sign out and back in.

Where these roles are assigned per user and per site is Managing users, roles and site access. The queue the editor→published floor gates is Reviewing and approving submissions; the one door around both the queue and the ladder above is Bypassing the queue: who can transition directly.