Read the lead-status summary
Follow this guide to use counts by configured lead status to understand the filtered pipeline. 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
Use counts by configured lead status to understand the filtered pipeline. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Apply the required lead criteria.
- Check each configured status count in the summary.
- Compare totals with the result table.
- Go to a representative lead from each status.
Fields and options to review
Configured statusesOne count per current lead status.
Filter scopeThe summary applies the same key report criteria and permission scope.
Rules the system enforces
- Summary counts are filter-dependent and should not be compared across different criteria without noting the filter.
How to confirm it worked
- The status-summary review 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.