Understand the collapsible-parent disable rule
This guide explains that why some Main Menu parents do not display a Disabled checkbox. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Menu Setup → Main Menu
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 you’ll accomplish
Know why some Main Menu parents do not display a Disabled checkbox. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to a collapsible parent’s options.
- Compare it with a non-collapsible item.
- Disable eligible children instead where appropriate.
Fields and options to review
Collapsible parentNo top-level disable control in the supplied Main Menu view.
Rules the system enforces
- This is an interface rule, not a permissions rule.
How to confirm it worked
- Understand the collapsible-parent disable rule 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.