Understand the absence of bulk actions
This guide explains that that the report table explicitly disables module bulk actions. 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 that the report table explicitly disables module bulk actions. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to the report.
- Check the table controls.
- Verify no module bulk-action selector is present.
- Use the supported core Leads workspace for authorised bulk operations.
Fields and options to review
bulk_actionsSet to false in the report table view.
Rules the system enforces
- Do not infer that hidden UI bulk actions are available through this module.
How to confirm it worked
- The bulk-action check 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.