Permissions Reference
Last updated: 2026-05-20
Every action in the Groups module is guarded by an RBAC permission check at the API gateway. The UI also queries your effective permissions and hides buttons you cannot use, so most users never see a denial. This page lists the permissions in resource:action form so administrators can grant them via RBAC policies.
Authorization is also influenced by your membership role on the specific group (OWNER, ADMIN, MODERATOR, ...). The UI combines the workspace permission and your group role when deciding what to show.
Group permissions
| Permission | What it allows |
|---|---|
group:read | Read group metadata, members, hierarchy, audit logs |
group:create | Create a new group (also creates an RBAC resource record) |
group:update | Update group configuration, manage hierarchy, archive / restore |
group:delete | Permanently delete a group |
group:export | Run the per-group export |
group:manage | Transfer ownership (OWNER-only by default) |
group:read is implicit for the owner, for non-PRIVATE groups, and for any member of the group.
Member permissions
| Permission | What it allows |
|---|---|
group-member:read | List members of a group, check membership |
group-member:create | Add members |
group-member:update | Change a member's role |
group-member:delete | Remove members |
Invitation permissions
| Permission | What it allows |
|---|---|
group-invitation:create | Send invitations |
group-invitation:update | Accept / decline pending invitations |
group-invitation:delete | Cancel pending invitations (admin-side) |
Setting permissions
| Permission | What it allows |
|---|---|
group-setting:create | Add a new key-value setting |
group-setting:update | Modify an existing setting |
group-setting:delete | Delete a setting |
Membership rule permissions
| Permission | What it allows |
|---|---|
group-rule:read | View rules and their execution history |
group-rule:create | Define a new rule |
group-rule:update | Modify a rule |
group-rule:delete | Remove a rule |
group-rule:execute | Trigger an on-demand rule sync |
Template permissions
| Permission | What it allows |
|---|---|
group-template:read | List and view templates |
group-template:create | Create a new template |
group-template:update | Edit a template |
group-template:delete | Delete a template |
Audit log permissions
| Permission | What it allows |
|---|---|
group-audit-log:read | Read a group's audit log entries |
Membership-role capability matrix
In addition to RBAC, your role on the group controls UI affordances. See 03-managing-members for the full grid.
Quick summary:
- OWNER — everything, including delete and transfer
- ADMIN — everything except delete and ownership transfer
- MODERATOR — member management only
- MEMBER — invite (if enabled) and read
- OBSERVER — read-only
- GUEST — limited external access
- BOT — programmatic actor; usually paired with App / Service entities
Public vs. self queries
A handful of queries are membership-scoped via @rbac(scopeType: "self"):
myGroups— only returns groups the actor belongs to- Membership checks on the viewer's own actor ID
Everything else is workspace-scoped via @rbac(scopeType: "wspace") and requires the workspace context header.
See also
- Managing members
- Group settings
- Spec:
../specs/06-permissions-authz.md