Discord-style roles with a permission grid for view, reply, edit, and manage actions
A Discord-style editor with one tab per role and a pivoted permission grid. Cells use a dropdown — Allowed or Not allowed — so every edit is explicit, discoverable, and undoable from the sticky save bar.
Click any editable cell to open a dropdown listing two options — Allowed and Not allowed. The cell updates the moment you make a choice. Plan-locked and operation-not-applicable cells stay non-editable, so the dropdown never appears on them.
This is a deliberate departure from a single-click toggle pattern: every edit is explicit and discoverable.
owner, admin, secretary, guest. Cannot be renamed or deleted. You can still edit their permissions — the server enforces the rest.
Use Create role in the left rail. Rename via the tab inline edit. Delete with the trash icon. The custom-role pattern is the place to model department-specific scopes.
As soon as you make a change, a sticky header appears at the top of the page with two buttons.
Ctrl+Ssave changesCtrl+Ddiscard
The Save button displays an inline spinner while the request is in flight and re-enables itself once the response lands. The header disappears automatically when no changes are pending.
Below the grid, three legend pills explain the cell colors at a glance:
Allowed — green checkNot allowed — muted minusNot applicable — amber lock
The amber chip carries a hover tooltip explaining why a cell is locked — plan limit or no underlying catalog key.
The admin dashboard exposes the same widget with scope="admin" for SUPERUSER staff editing global system roles. The org-scoped view at /roles:
organizationId = caller.orgId and never sees a global system-role mode.Everything else — the role rail, the permission grid, the dropdown editor, the save flow — behaves identically.