Understand current-user row highlighting
This guide explains that why some lead rows receive an alert highlight for globally privileged viewers. 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
Know why some lead rows receive an alert highlight for globally privileged viewers. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Run the report as a user with global Leads View.
- Find a lead assigned to the signed-in user.
- Compare its row styling with leads assigned to other staff.
Fields and options to review
Highlight conditionRow is assigned to the current user while the user has global view.
Rules the system enforces
- Highlighting is presentation only and does not alter ownership or priority.
How to confirm it worked
- The row-highlight 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.