Security, limitations and troubleshooting
Understand permission and implementation limits and resolve common empty, missing or unexpected results.
Guides in this workflow
Follow the guide that matches the exact action, filter, menu change or issue.
Understand the Create-capability limitation
Create is registered but not separately checked in the save-template branch after View access.
Understand the template-update ID limitation
The model update condition uses the template ID after the controller load and does not independently add staff ownership.
Understand the inline status-action permission limitation
The module’s status endpoint has its explicit edit-permission check commented out.
Troubleshoot an empty lead report
Criteria may conflict, the default This Month period may be too narrow, or lead scope may exclude records.
Troubleshoot a missing Staff Member filter
The selector requires global core Leads View.
Troubleshoot custom lead date results
The report filters only Created Date or Last Contact, and equal boundaries use equality.
Troubleshoot a lead template that does not load
The filter ID must be numeric, owner-scoped and loaded without a POST request.
Troubleshoot the lead template-name message
The browser requires a non-empty name when Save Filter Template is selected.
Understand the absence of shared lead templates
Templates are stored and listed by staff owner.
Understand unsupported lead-filter automation
No cron, API, webhook, scheduled email, PDF generator or module import/export scheduler is registered.
Understand migrations 101–114
Migration classes are supplied but all up methods are empty.
Verify Advanced Lead Filters after deployment
Run a controlled report, summary, inline status and template test.