Setup, version, access and architecture

Understand Letter Manager menu and hook integration

Know where the module appears for staff, customer profiles and logged-in clients.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager; Admin Area → Customers → Open customer → Letter History; Client Area → Letter History

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

Know where the module appears for staff, customer profiles and logged-in clients. 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 staff sidebar and confirm Letter Manager with Dashboard, Templates and Settings.
Open a customer profile and select Letter History.
Sign in as a client contact and confirm Letter History appears in the client menu.

Fields, choices and supported possibilities

Action scopeKnow where the module appears for staff, customer profiles and logged-in clients.

Module version1.0.0

Exact routeAdmin Area → Letter Manager; Admin Area → Customers → Open customer → Letter History; Client Area → Letter History

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 staff sidebar uses the letter-manager parent with three children.
The admin customer-profile tab is registered at position 50.
The client menu item is added only when a client contact is logged in.

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.