Understand the collapsible-parent disable rule
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 some Main Menu parents do not display a Disabled checkbox.
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 this guide helps you do
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
Collapsible parentNo top-level disable control in the supplied Main Menu view.
Rules and limits
- This is an interface rule, not a permissions rule.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.