Sent-letter history and staff actions

Review an enclosure in Internal Full View

Open or download the optional file stored with the letter.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Internal Full View → Enclosed Attachment

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

Open or download the optional file stored with the letter. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm the displayed file name, size and MIME.
Select Open Enclosed File or Download.
Verify it matches the intended attachment.
If the file is missing, investigate storage/retention rather than assuming it was delivered.

Fields, choices and supported possibilities

Action scopeOpen or download the optional file stored with the letter.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Internal Full View → Enclosed Attachment

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 buttons appear when a stored enclosure path exists.
The view separately checks whether the file exists on disk.

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.