Understand why menu visibility is not permission
A disabled menu entry is hidden from navigation but the module does not revoke route or record permissions.
Exact navigationAdmin Area → Setup → Menu Setup
Before you begin
- Confirm 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 covers
A disabled menu entry is hidden from navigation but the module does not revoke route or record permissions. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Reproduce the behaviour with a controlled administrator account.
- Use CRM roles/capabilities to control access and use the builder only for navigation presentation.
- Test the resulting navigation with an administrator and a restricted staff account.
- Reset or restore the intended menu configuration after the test.
Fields, choices and supported possibilities
Verified behaviourA disabled menu entry is hidden from navigation but the module does not revoke route or record permissions.
Code-backed validations and workflow rules
- A disabled menu entry is hidden from navigation but the module does not revoke route or record permissions.
Expected result and verification
- Understand why menu visibility is not permission 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.