Understand new menu items after a CRM or module update
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 how newly introduced unsaved entries are handled.
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 this guide helps you do
Know how newly introduced unsaved entries are handled. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to the relevant Main Menu or Setup Menu builder.
- Make one controlled change that demonstrates the rule.
- Save and reload the CRM navigation.
- Reset after the test when the change is not required.
Fields and options
Code-backed ruleRuntime menu items absent from saved JSON are appended rather than discarded.
Rules and limits
- Runtime menu items absent from saved JSON are appended rather than discarded.
Check it worked
- Understand new menu items after a CRM or module update 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.