Roles & permissions (admin UI)

Purpose

Administrators manage IAM roles from Setting → Roles & Permission (/dashboard/setting/roles-permission). Data is loaded with api.OrgRoles.get; deletes call api.OrgRoles.delete.

Who uses it

Security administrators and tenant super-admins adjusting role catalogs.

Prerequisites

• Route guard expects role view/list permissions (view_role, list_role).
• Creating or editing routes (/roles-permission/new, /roles-permission/$roleId) require matching create/update permissions inside the forms (CanI gates individual controls).

Navigation

1. Sidebar → Setting → Roles & Permission.
2. Use search and filters (scope, status).
3. Select New when available to open /dashboard/setting/roles-permission/new.
4. Open an existing role row to edit at /dashboard/setting/roles-permission/$roleId.

Expected results

• Table lists roles returned by the API.
• Successful delete refreshes the grid via React Query invalidation.

Troubleshooting

• Empty list: Confirm filters or insufficient roles in the tenant — contact support if configuration should exist.
• Cannot create/edit: Escalate permission grants for role management codes.

Related

• Permissions — end-user explanation of access denied and route requirements.
• User management