Setup, version, access and architecture

Open the Letter Manager dashboard

Use the main workspace for creating correspondence and managing sent-letter history.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Dashboard

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

Use the main workspace for creating correspondence and managing sent-letter history. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Sign in to the staff admin area.
Open Letter Manager in the main sidebar.
Select Dashboard.
Confirm the existing-customer and external-recipient tabs and Sent Letters History are visible.

Fields, choices and supported possibilities

Action scopeUse the main workspace for creating correspondence and managing sent-letter history.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Dashboard

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

Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
Browser controls are not a substitute for server-side and operational verification.

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.