Find administration screens
The application splits administration across Authorization, Organization, Settings and the separate operator console. The title on the Authorization landing page is not a complete tenant setup wizard.
Screen map
| Area | Application route | Purpose |
|---|---|---|
| Authorization | /admin-panel | Entry to user, role and permission work |
| Users | /admin-panel/user | Search, create, view and maintain permitted users |
| User detail | /admin-panel/user/user-detail/:id | Inspect one user and permitted actions |
| Roles | /admin-panel/role | Search, create and maintain roles |
| Role detail | /admin-panel/role/role-detail/:id | Inspect one role |
| Permissions | /admin-panel/permission | Read the permission catalogue |
| Assign roles | /admin-panel/assign-role | Replace a user's role set |
| Assign permissions | /admin-panel/assign-permission | Replace a role's permission set |
| User business unit access | /admin-panel/user-business-unit-access | Assign units and primary operating unit |
| Business units | /organization/business-units | Maintain operating structure |
| Hierarchy | /organization/business-unit-hierarchy | Review parent/child structure |
| Settings | /settings | Entry to capability and master-data settings |
| Tenant capabilities | /settings/tenant-modules | Modules and per-module feature configuration |
| Appearance | /settings/appearance | Draft, preview and publish tenant styling |
| Operator console | /operator | Separate platform account and tenant governance |
| Setup completion | /account-setup | Accept a valid private invitation/recovery token |
Routes in this guide are paths inside the application, not links in this documentation site. Replace :id with the record selected through the application. A route is not an access bypass.
Find a record
- Open the relevant register.
- Enter a distinctive username, role name or permission code in its search field.
- Check pagination if the expected record is not visible.
- Open the detail/view action and confirm the target before editing.
- If loading fails, use Retry where offered. Do not treat the failed list as an empty catalogue.
The legacy /organization/user-business-unit-access path redirects to Authorization. Master data formerly under /admin-panel/master-data now routes to Settings. Prefer current navigation/bookmarks.
Example: Nadia wants to change which branches Farah can use. She opens User business unit access, not Assign roles. A role edit changes permitted operations for everyone holding that role; a unit assignment changes Farah's operating scope.
Older /manage-users and /manage-admin routes also exist. This guide uses the Authorization workspace for routine account and role maintenance and records lock/recovery separately; it does not assume identical actions across older screens.