Filter leads by city
Limit the report using stored lead city values. 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
Limit the report using stored lead city values. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to the lead report.
- Find City.
- Select one or more listed cities.
- Apply the filter.
- Go to a returned lead to verify its stored address value.
Fields and options to review
CitySelect one or more listed cities.
UnknownAvailable as an explicit data-quality choice.
Rules the system enforces
- City Unknown includes blank or null city values.
How to confirm it worked
- Filter leads by city 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.