Understand the “Search Clients & Leads” label limitation
Avoid expecting CRM leads to appear in a selector that the supplied controller populates only from customers.
Exact navigationAdmin Area → Letter Manager → Dashboard → Search Clients & Leads
Before you begin
- Use an authorised account and confirm the customer, external recipient, template, letter or configuration is the intended one.
- Follow the exact route shown above and verify the stored record, generated file and delivery evidence instead of relying on an alert alone.
What this guide covers
Avoid expecting CRM leads to appear in a selector that the supplied controller populates only from customers. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.
Exact step-by-step process
- Open the recipient selector.
- Search for an existing CRM customer/company.
- Use Manual Entry (External) when the intended recipient is not a customer.
- Do not expect a CRM lead record to be loaded by this release.
Fields, choices and supported possibilities
Action scopeAvoid expecting CRM leads to appear in a selector that the supplied controller populates only from customers.
Module version1.0.0
Exact routeAdmin Area → Letter Manager → Dashboard → Search Clients & Leads
EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.
Code-backed validations and workflow rules
- The index action queries clients joined to their primary contacts.
- Each option is emitted with type client.
- send_letter parses the value but uses the numeric ID as a client ID and does not load a lead.
Expected result and verification
- The requested letter, template, setting, file or tracking detail is created or updated through the supported route.
- The history row, generated PDF, email/send metadata, public verification, signature evidence, client view or postal display agrees with the action.
- Any warning, missing file or failed send is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify recipient identity before sending or exposing public links.
- Protect PDFs, enclosures, signatures, verification URLs, email-open metadata, IP addresses and customer data under organisational policy.
- Test configuration and deployment changes with controlled records before production-wide use.
- Interpret email opens and e-signatures according to their documented technical limitations.
Important code-backed limitationDespite the tab label, the supplied v1.0.0 code does not populate or process CRM lead records.