Email delivery, attachments and read receipts

Understand Letter Manager email audit fields

Review who sent the message, where it was sent and when the send succeeded.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Internal Full View

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

Review who sent the message, where it was sent and when the send succeeded. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Review Email Sent, Email Sent To and Email Sent At.
Review the sent-by staff ID through authorised record inspection.
Link the ID to the responsible staff account where necessary.

Fields, choices and supported possibilities

Action scopeReview who sent the message, where it was sent and when the send succeeded.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Internal Full View

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

sent_by_staff_id is updated on every send attempt after email->send.
Email Sent At is populated only when send() returns true.
The current UI does not display an email CC field or allow entering CC despite the schema column.

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.