readonly role
This commit is contained in:
@@ -28,10 +28,11 @@ All capabilities live in the `ApiCapability` enum. The current list is:
|
||||
|
||||
## Default Sets
|
||||
|
||||
Provisioning (and the test harness) seed three system capability sets per tenant:
|
||||
Provisioning (and the test harness) seed four system capability sets per tenant:
|
||||
|
||||
- `owner` — contains the full set above. Tenant owners, admin users, and freshly minted API tokens effectively get unrestricted access.
|
||||
- `user` — the default interactive role: full document/tag/correspondent/profile access, but no capability-set or WebDAV write privileges.
|
||||
- `readonly` — interactive but read-only: document/folder/tag/correspondent reads plus WebDAV downloads, but no modifying routes.
|
||||
- `webdav` — contains only `webdav:read`. WebDAV backup scripts can bind to this set for read-only access.
|
||||
|
||||
System sets are flagged with `is_system = true` and cannot be modified or deleted via the API.
|
||||
|
||||
Reference in New Issue
Block a user