Change lead status from filtered results
Use the inline status dropdown and understand its dependency on core lead rules.
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 the inline status dropdown and understand its dependency on core lead rules. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Run the report.
- Locate the Status column.
- Open the inline status dropdown.
- Choose the new status.
- Wait for the status cell to refresh and open the lead to verify the change.
Fields, choices and supported possibilities
Status dropdownCalls the core lead_mark_as action, then refreshes status HTML after approximately 300 ms.
Code-backed validations and workflow rules
- The module controller does not add a separate active edit-permission check at this endpoint; core lead functions/configuration must enforce the allowed transition.
- Converted leads may be locked when lead_lock_after_convert is enabled and the user is not an administrator.
Expected result and verification
- Changing lead status 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.
- Test role behaviour and converted-lead locking before permitting operational use.