Understand the Create-capability limitation
Follow this guide to create is registered but not separately checked in the save-template branch after View access.
Where to goAdmin Area → Lead Filters → Lead Filters
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
Create is registered but not separately checked in the save-template branch after View access. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour using known test leads and a controlled role.
- Grant View only to staff who may save templates or apply a reviewed code correction.
- Compare with the core Leads workspace.
- Record the verified outcome before changing permissions or code.
Fields and options
Verified behaviourCreate is registered but not separately checked in the save-template branch after View access.
Rules and limits
- Create is registered but not separately checked in the save-template branch after View access.
Check it worked
- Understand the Create-capability limitation 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.