Understand current-user row highlighting
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that why some lead rows receive an alert highlight for globally privileged viewers.
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 this guide helps you do
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
Highlight conditionRow is assigned to the current user while the user has global view.
Rules and limits
- Highlighting is presentation only and does not alter ownership or priority.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.