Understand protected Setup Menu items
This guide explains that which critical Setup entries cannot be disabled by default. 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 → 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 you’ll accomplish
Know which critical Setup entries cannot be disabled by default. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to Setup Menu.
- Find Menu Setup, Main Menu, Modules and Settings entries.
- Verify protected entries have no disable control.
Fields and options to review
Default protected slugssetup-menu-options, main-menu-options, modules and settings.
Extension hooksetup_menu_no_disable_items can add protected slugs.
Rules the system enforces
- Protection prevents the builder from hiding its own access, Modules or Settings.
How to confirm it worked
- Understand protected Setup Menu items 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.