Sent-letter history and staff actions

Understand every Sent Letters History action

Follow this guide to use each icon for its implemented purpose. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Jump to steps

Where to goAdmin Area → Letter Manager → Sent Letters History → Options

Before you start

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 you’ll accomplish

Use each icon for its implemented purpose. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Follow these steps

Use signature status icon when signature is required.
Use envelope icon to resend email.
Use PDF icon to open the generated file.
Use eye icon for Internal Full View.
Use QR icon for public verification.
Use task icon for the native task modal.
Use truck icon for postal tracking.

Fields and options to review

Action scopeUse each icon for its implemented purpose.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Options

EvidenceVerify the history row, PDF, email metadata, open evidence, signature, public page, client view or postal fields produced by this flow.

Rules the system enforces

No edit, duplicate, void or delete icon is implemented for letter records.
Actions operate on the existing record ID and stored public tokens.

How to confirm it worked

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.

Was this guide useful?Your response is stored only in this browser.