Understand CRM Menu Builder option storage
This guide explains that how both menu definitions are stored without module tables. 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
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 how both menu definitions are stored without module tables. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Use the Main Menu and Setup Menu screens to inspect and save configuration.
- Verify the menu persists after a page reload.
- Use Reset rather than direct database edits when returning to defaults.
Fields and options to review
aside_menu_activeJSON for sidebar positions, icons, disabled states and children.
setup_menu_activeJSON for Setup Menu positions, icons, disabled states and children.
Rules the system enforces
- The values are application-managed JSON.
- There are no module-specific database tables.
How to confirm it worked
- The storage review 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.
- Do not hand-edit the JSON in production.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.