Manage the Controller menu

Before you start

• Confirm the staff roles and permissions model.
• List the pages used every shift and the pages used only by supervisors.
• Use an owner/admin account to change menu structure.

Use menu management for clarity

The sidebar should help staff move quickly. It should not become a hiding place for pages that are still accessible through permissions.

• Group common work such as Store, Reports, Setup, and Agent Tools.
• Keep daily pages visible for the staff who need them.
• Avoid burying emergency or health pages too deeply.

Use parent menus carefully

Parent menus can keep the sidebar clean when a branch uses many features. Keep names simple and match the words staff use.

• Use standard parent groups where they already fit.
• Create custom groups only when they reduce confusion.
• Review child pages after moving a section.

Separate menu visibility from access

A hidden page is not the same as a blocked page. Sensitive work should be protected by permissions even if it is also hidden from the normal sidebar.

• Use permissions for real access control.
• Use menu visibility for navigation cleanup.
• Test with a staff account after changing the menu.

Verify it worked

• The sidebar groups match the staff workflow.
• Daily pages are easy for staff to find.
• Sensitive pages remain protected by permissions.

Troubleshooting

Related product pages

• Controller

See also

• Invite staff and assign roles
• Set Controller language
• Configure permissions and page access