You may see users reporting that their menu options have changed, for example, screens they could previously access have disappeared, or new screens have appeared.
This usually happens when changes have been made to menu access, roles, or BCode assignments.
How you assign menu access depends on whether your organisation is fully non‑Spine, fully Spine-enabled, or waiting to be connected to Spine.
Key behaviour to understand
If your organisation is configured to use Spine, but has not yet been connected, menu access must be assigned at BCode level using the RBAC BCode Management screen.
If you incorrectly assign Roles to menu items instead, the system will automatically apply those permissions to all BCodes linked to the Role, which may cause unexpected access changes.
Example of unintended access changes
Menu item has Role R8001.
Role R8001 is linked to BCodes B0001 and B0002.
You add a second Role linked to B0033.
Once saved:
B0033 now gets access intended for B0001 and B0002
B0001 and B0002 now get access intended for B0033
This is why customers awaiting Spine connection must not assign menu access via Roles.
Correct menu assignment by customer type
Customers fully non‑Spine
Assign menu access using the Roles button against the menu item in Menu Configuration.
Customers fully Spine‑enabled
Assign menu access using BCodes only, via the RBAC BCode Management screen.
Customers set up for Spine but still logging in with username and password
Assign menu access using BCodes, via the RBAC BCode Management screen.
Summary
Non‑Spine customers: assign access using Roles in Menu Configuration.
Spine customers connected or awaiting connection: assign access using BCodes in RBAC BCode Management.
Assigning access incorrectly e.g., adding Roles to Spine menus can give users unintended access.