# Content-level permission overrides

URL: https://kywi-docs-production.up.railway.app/governing/content-level-permission-overrides
Type: docPage

A content-level grant only restricts a document once the first one exists — with none, a page stays open to anyone your role already lets read it.

A content-level permission is a grant — one user or one group, plus a single action — attached to one document. With zero grant rows the document stays open to anyone whose role already covers that action; adding the *first* grant is what switches the document from open-by-role to closed-by-default for everyone else.

## Who a grant can restrict

[Site admins and super admins](/governing/roles-and-the-capability-matrix/) bypass document-level permissions entirely, on reading and on every mutation. A grant can hold back an author or an editor; it can never hold back a site admin.

## A mutation needs two grants, not one

Publishing, editing or deleting a permissioned document requires both a read grant and the action-specific grant, on the same document. A grant that only covers publish, on a document the user has no read grant for, does nothing — they still can't act on a page they can't see.

A single grant targets exactly one user or one group, never both, and the database itself — not application code — refuses a duplicate grant for the same target and action.

## The last grant reopens the document immediately

Access is recomputed on every check, not cached against the document once. Revoke a document's last remaining grant and it goes straight back to open-by-role for everyone else — there is no separate "re-enable open access" step, and nothing to wait out before it takes effect.

## Managing overrides is a site-admin action

Granting or revoking a content-level override is itself gated at site admin, even when the access being handed out only needs author or editor. Setting up a narrower grant for someone else is a more privileged action than the access that grant confers.
