Skip to content

docs(auth): granular admin permissions go through authz.check() #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zumbrunn merged 2 commits into from
Aug 31, 2026
Merged

docs(auth): granular admin permissions go through authz.check() #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0b2046a
docs(auth): granular admin permissions go through authz.check()
zumbrunn Aug 30, 2026
cec6c16
docs(auth): drop removed users.manage from authz action table
zumbrunn Aug 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions 17.authentication/03.authorization/default.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,8 @@ Dune's default schema defines:
|--------|-------------|
| `access` | member, admin, editor, author |
| `edit` | owner, admin, editor |
| `pages.update` | admin, editor |
| `users.manage` | admin |
| `pages.update` | admin, editor, author |
| `users.update` | admin |
| `media.upload` | admin, editor, author |

## Config
Expand Down Expand Up @@ -235,11 +235,11 @@ editor → tuple: (user:bob, editor, app:admin)
author → tuple: (user:carol, author, app:admin)
```

The admin panel middleware enforces panel access via `authz.check()` when authz is wired. Role changes and user deletes via the admin API automatically sync the tuple store.
The admin panel middleware enforces panel access via `authz.check()`. If `authz` is undefined (creation failed at startup), the gate fails closed (403). Role changes and user deletes via the admin API automatically sync the tuple store.

**Granular admin permission checks** (`pages.create`, `config.read`, etc.) still use the flat `ROLE_PERMISSIONS` model — full polizy migration for those is tracked in the later roadmap.
**Granular admin permission checks** (`pages.create`, `config.read`, etc.) use the same `authz.check()` against `{ type: "app", id: "admin" }`, mapped through the canonical `actionToRelations` schema. There is no parallel role table.

## Limitations

- `authzStore: local` is single-process only. Multi-process deployments should use a shared database (future `authzStore: db`).
- Granular admin permissions (`pages.create`, `config.read`, etc.) — not yet through polizy. `ROLE_PERMISSIONS` remains the authority for those.
- The published synchronous hook `ResponseTransformContext.auth.hasPermission()` is a role-only approximation of that schema (`roleHasPermission()`). Use `authz.check()` for access decisions.