The job of this console
Hide a module from everyone, or allow only HR Admin and Admin on a sensitive page. Preview who will still see the menu. Roles still decide permissions inside a page.
Admin · Access & approvals
Persona Navigation
Turn things off for everyone, or pick a page and choose which personas can open it. Saves to org Application Config.
Scroll to Flowcharts for Turn off vs Page access. Scenario guide: Turn off org access or customize page personas. Related: Admin & Access.
Who may open a page
Org-wide off, or a page-by-page persona set
Persona navigation turns things off for everyone, or picks a page and chooses which personas can open it. Saves to org Application Config — not a local browser preference.
Admin → Persona navigation
Route
/admin/persona-navigation
Org flag personaNavigationEnabled
HR Admin · Org Admin
Seat at the table
Administrators. A manager who cannot see Payroll should not be ‘fixed’ by giving them Admin — change the persona set here if the page should be wider.
The working rhythm
Pick a page, set personas, save, then log in as a test persona and confirm the sidebar. Coordinate with feature flags: a flag off still hides the page for everyone.
Moments that bring you here
A new analytics page that should be executives only. Contractors seeing Admin. After adding a persona. When a pilot group should not see payroll.
ⓘ
Saves into Application Config
This is org policy, not a personal pin. Roles & permissions still own the RBAC matrix inside screens.
Interactive data flow
Toggle personaNavigationAdditional kills, pagePersonaMap, and role personas — see effective sidebar and route guards.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Turn off access for everyone
Kill a persona, module, or individual page org-wide without editing Roles.
flowchart TD
A[Open Persona navigation] --> B[Turn off tab]
B --> C{What to hide?}
C -->|Persona| D[Toggle persona Off]
C -->|Module| E[Toggle module Off]
C -->|Page| F[Search + turn page Off]
D --> G[Save changes]
E --> G
F --> G
G --> H[Users refresh — item hidden]
- 1Open Persona navigationAdmin → Persona navigation with personaNavigationEnabled on.
- 2Turn off tabFirst tab: org-wide kill switches for personas, modules, and pages.
- 3What to hide?Choose persona, module strip, or search the page list.
- 4Toggle OffDisabled entries always win over Roles and page maps.
- 5Save changesWrites org.json
personaNavigationAdditionaldisable lists. - 6Users refreshKilled personas/pages stay hidden after login or hard refresh.
2 — Customize which personas open a page
Product default (sidebar catalog) vs Custom persona set for one route.
flowchart TD
A[Page access tab] --> B[Select one page]
B --> C{Mode?}
C -->|Product default| D[Use catalog personas]
C -->|Custom| E[Toggle personas]
E --> F[Save pagePersonaMap]
D --> G[Empty override = catalog]
F --> H[Org override for that path]
G --> I[Sidebar + route guard]
H --> I
- 1Page access tabSecond tab: edit one page at a time.
- 2Select one pageFilter by search, group, or overrides-only.
- 3Mode?Product default keeps sidebar catalog personas; Custom seeds an override.
- 4Toggle personasAllow only the personas that should open that route.
- 5Save pagePersonaMapStored under
personaNavigationAdditionalin Application Config. - 6Sidebar + route guardMenus and deep links respect the map after role persona modules.
Roles vs Persona navigation
| Question | Use Roles (/admin/roles) | Use Persona navigation |
|---|---|---|
| Which personas may this role switch to? | ✓ Persona access tab → personaModules | — |
| Hide DELIVERY org-wide for everyone? | Link to Persona navigation | ✓ Turn off tab |
| Only MANAGER may open Leave page? | ✓ Page preview (writes org map) | ✓ Page access tab |
| Module CRUD matrix? | ✓ Advanced tab | — |
Interactive trace: Roles simulator (role layer) · Persona navigation simulator (org layer).
Overview
Admin → Persona navigation is the simplified org editor for access kill switches and per-page persona maps. Role-level “who may use a persona” still lives on Roles & permissions. Protected paths (Roles, Persona navigation, App Config, Setup checklist) cannot be turned off.
Evaluation order: role menu flags → role personaModules → org pagePersonaMap when present → org disable lists (always win).
How to use
1. Enable the screen
Confirm
personaNavigationEnabled (or Roles access) for your admin role.2. Turn off what the org should not see
On Turn off, disable personas, modules, or search and turn individual pages Off.
3. Customize a page when needed
On Page access, select a route, choose Custom, toggle personas, then Save.
4. Verify with a test user
Sign in as a non-admin persona and confirm menus and deep links match the policy.