Troubleshoot an item that returns after saving
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
New runtime items absent from saved JSON are appended, and protected items cannot be disabled.
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
New runtime items absent from saved JSON are appended, and protected items cannot be disabled. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour with a controlled administrator account.
- Verify the item’s slug/state and whether it is protected or newly introduced.
- Test the resulting navigation with an administrator and a restricted staff account.
- Reset or restore the intended menu configuration after the test.
Fields and options
Verified behaviourNew runtime items absent from saved JSON are appended, and protected items cannot be disabled.
Rules and limits
- New runtime items absent from saved JSON are appended, and protected items cannot be disabled.
Check it worked
- Troubleshoot an item that returns after saving 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.