Disable an eligible Setup Menu child
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Hide an eligible child entry.
Where to goAdmin Area → Setup → Menu Setup → Setup 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
Hide an eligible child entry. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to child options.
- Select Disabled.
- Save and verify.
Fields and options
Protected childNo disable checkbox when its slug is protected.
Rules and limits
- Do not attempt to hide a protected safety entry through request manipulation.
Check it worked
- Disable an eligible Setup Menu child 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.