Security, privacy, limitations and troubleshooting

Understand Letter Manager API, webhook and cron limitations

Do not document or promise integration endpoints that are not supplied.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationCode-backed reference → Letter Manager module

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

Do not document or promise integration endpoints that are not supplied. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Use the staff UI and public routes described in this guide set.
Use native email and task integration only where implemented.
Plan separately for API, webhook, queue, scheduled dispatch or external courier integration.

Fields, choices and supported possibilities

Action scopeDo not document or promise integration endpoints that are not supplied.

Module version1.0.0

Exact routeCode-backed reference → Letter Manager module

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

No REST API, OpenAPI specification, webhook sender/receiver or cron hook is registered.
The public email-open route is a tracking pixel, not an API.

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.