Understand the collapsible-parent disable rule
Know why some Main Menu parents do not display a Disabled checkbox.
Exact navigationAdmin Area → Setup → Menu Setup → Main Menu
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 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.
Exact step-by-step process
- Open a collapsible parent’s options.
- Compare it with a non-collapsible item.
- Disable eligible children instead where appropriate.
Fields, choices and supported possibilities
Collapsible parentNo top-level disable control in the supplied Main Menu view.
Code-backed validations and workflow rules
- This is an interface rule, not a permissions rule.
Expected result and verification
- 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.