Assign Advanced Lead Filters permissions
Grant View and understand the separately registered Create capability. 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 → Staff → Roles → Open role → Permissions
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
Grant View and understand the separately registered Create capability. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to the intended staff role.
- Find Advanced Lead Filters.
- Enable View for report/menu access.
- Enable Create only where policy requires it.
- Save and test using that staff account.
Fields and options to review
ViewExplicitly checked by the controller.
CreateRegistered but not separately checked in the template-save branch.
Rules the system enforces
- Treat View as including the current ability to save personal templates.
- Core Leads permissions independently control visible and editable lead records.
How to confirm it worked
- Permission assignment 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.