Understand the Create-capability limitation
Follow this guide to create is registered but not separately checked in the save-template branch after View access. 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 → 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 you’ll accomplish
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 to review
Verified behaviourCreate is registered but not separately checked in the save-template branch after View access.
Rules the system enforces
- Create is registered but not separately checked in the save-template branch after View access.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.