Understand which leads a staff member can see
Apply the module’s exact lead-visibility condition.
Exact navigationAdmin Area → Lead Filters → Lead Filters
Before you begin
- Confirm 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 covers
Apply the module’s exact lead-visibility condition. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Check whether the user has global core Leads View permission.
- Run a broad report as that user.
- Compare results with the core Leads list under the same account.
- Test an assigned, self-created, public and unrelated private lead.
Fields, choices and supported possibilities
Without global Leads ViewIncludes leads assigned to the user, added by the user or marked public.
With global Leads ViewCan include all matching leads and exposes the optional staff-member filter.
Code-backed validations and workflow rules
- The module does not elevate lead access.
Expected result and verification
- The scope comparison 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.