Setup, version, access and architecture

Understand Letter Manager routes and public endpoints

Map staff, client, verification, read-receipt and signature paths without treating technical endpoints as menu pages.

Audience: Administrators and developersPermission: Authenticated staff accountModule v1.0.0

Exact navigationCode-backed reference → Letter Manager routes and controllers

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

Map staff, client, verification, read-receipt and signature paths without treating technical endpoints as menu pages. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Use admin/letter_manager for the dashboard.
Use letter_manager/verify/{unique_code} for public verification.
Allow letter_manager/email_open/{token} only as the embedded tracking-pixel endpoint.
Use the client letter-history routes only after client login.
Use letter_manager/letter_signature/index/{hash} only through the recipient signature link.

Fields, choices and supported possibilities

Action scopeMap staff, client, verification, read-receipt and signature paths without treating technical endpoints as menu pages.

Module version1.0.0

Exact routeCode-backed reference → Letter Manager routes and controllers

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

Invalid public verification or signature identifiers return 404.
The email-open endpoint always returns a 1×1 GIF, including invalid-token cases.
A direct admin customer-tab route also maps to admin/letter_manager/client/{client_id}.

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.