Setup, version, access and architecture

Understand Letter Manager data ownership

Identify records and files created by the module before setting retention, backup or deletion policy.

Audience: Administrators, auditors and developersPermission: Authenticated staff accountModule v1.0.0

Exact navigationCode-backed reference → Letter Manager installation schema and uploads/letter_manager

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

Identify records and files created by the module before setting retention, backup or deletion policy. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Inventory history, template and email-open tables.
Inventory PDFs, signatures and enclosure files under uploads/letter_manager.
Map stored recipient, email, IP, user-agent and signature data to the organisation’s retention policy.
Test authorised export or deletion procedures outside the normal module UI.

Fields, choices and supported possibilities

Action scopeIdentify records and files created by the module before setting retention, backup or deletion policy.

Module version1.0.0

Exact routeCode-backed reference → Letter Manager installation schema and uploads/letter_manager

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 normal UI does not provide record deletion, voiding or retention automation.
Deactivating the module does not remove tables or files in the supplied code.
Backups and error_log files shipped inside the source archive are development/runtime artefacts, not user features.

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.