Read the lead-status summary
Use counts by configured lead status to understand the filtered pipeline.
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
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.
Exact step-by-step process
- Apply the required lead criteria.
- Review each configured status count in the summary.
- Compare totals with the result table.
- Open a representative lead from each status.
Fields, choices and supported possibilities
Configured statusesOne count per current lead status.
Filter scopeThe summary applies the same key report criteria and permission scope.
Code-backed validations and workflow rules
- Summary counts are filter-dependent and should not be compared across different criteria without noting the filter.
Expected result and verification
- 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.