Skip to main content
Role Navigation narrows the sidebar so a nurse is not scrolling past claims and a records officer is not scrolling past theatre. It governs pages, not actions: what someone may do on a page they can open stays with their staff permissions.

​
What this tab controls

Two cards, and they are separate on purpose. While the master switch is off, the editor tells you so rather than letting you tune rules that do nothing: “Role-scoped navigation is switched off, so these rules are not being applied yet. Configure them here, then turn the switch above on when ready.”

​
Set it up

1

Configure first, switch on last

Leave Scope navigation by role off while you work. Rules you save are stored but inert until the switch is on, so there is no window where half a configuration is live.
2

Pick a role

Select a role in the left list. Its checkboxes load from wherever it lives now — a saved override, otherwise the shipped default.
3

Tick what that role works in

Work down the grouped checkboxes. The line above them names the landing page as you go — “Lands on Nursing Station after sign-in”, and so on.
4

Save that role, then do the next

Select Save. It confirms with the role’s name — “Nurse navigation saved”. Each role saves on its own; moving to another role never carries your ticks across.
5

Turn the master switch on

Go back to Role-based navigation and switch Scope navigation by role on. You get “Role-based navigation on” and “Signed-in staff see the change within 5 minutes.”

​
What changes once you save

Hiding a module is a convenience, not a security control. The card says it outright: “This changes navigation only — it is not a security control. What each person may read and write is still decided by their permissions.” Someone who should not be able to do a thing must be stopped by their permissions, not by an absent menu item — the server checks on every action regardless of what the sidebar shows.

​
Check it worked

Turn the master switch on, wait five minutes, then have someone in a narrowed role sign out and back in. Their sidebar should carry only the modules you ticked, and they should land on the first one. Ask them to paste a link to something you unticked: they should be returned to their own area rather than seeing an error. Back in the editor, the roles you changed should read Custom.

​
Common issues

Two likely reasons. The master switch Scope navigation by role is still off — the amber note in the editor says so. Or it is on and you are inside the five-minute window; changes reach signed-in staff within 5 minutes.
Deliberate, not a bug. They are never narrowed by these rules, so they are absent rather than shown greyed out.
Rules match at their own level, so the insurance dashboard, pre-authorisation and claims move together. One checkbox is honest about that; three would not be.
The landing page is the first ticked module in navigation order, and the editor names it above the checkboxes. Untick things above the one you want, or accept the order the sidebar uses.
It stays disabled until you change something, and with every box unticked — a role with nothing is not a valid state. Tick at least one module.
Expected. Hiding is navigation only. Stop the action itself with their permissions.
For the roles themselves and what each one is for, see Roles.