Understand administrator-only access
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that why staff roles do not receive a CRM Menu Builder capability.
Where to goAdmin Area → Setup → Menu Setup
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide helps you do
Know why staff roles do not receive a CRM Menu Builder capability. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Sign in with a non-administrator test account.
- Verify Menu Setup is not available.
- Sign in as an administrator and confirm both builders are available.
Fields and options
Controller guardUses the CRM administrator check.
Custom capabilitiesNone registered.
Rules and limits
- Do not expose the controller to non-administrators through navigation changes.
Check it worked
- The access test completes without a validation or permission error.
- The refreshed report, menu or saved-template page shows the expected state.
- A second authorised user sees only the records and navigation allowed by their core CRM permissions.
Security, privacy and operational checks
- Test changes with a non-production record or a controlled administrator account before wider rollout.
- Do not use navigation visibility as a substitute for core CRM record permissions.
Related guides
Was this guide useful?Your response is stored only in this browser.