Understand runtime menu-filter priorities
Know when options/icons/visibility and positions are applied.
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
Know when options/icons/visibility and positions are applied. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open the relevant Main Menu or Setup Menu builder.
- Make one controlled change that demonstrates the rule.
- Save and reload the CRM navigation.
- Reset after the test when the change is not required.
Fields, choices and supported possibilities
Code-backed ruleCustom options filters run at priority 999; custom position filters run at priority 998 for sidebar and Setup menus.
Code-backed validations and workflow rules
- Custom options filters run at priority 999; custom position filters run at priority 998 for sidebar and Setup menus.
Expected result and verification
- Understand runtime menu-filter priorities 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.