Setup, version, access and architecture

Install and activate Letter Manager v1.0.0

Run the portable installer, create module-owned tables and storage, then verify the three registered menu pages.

Audience: CRM staffPermission: Administrator / module-management accessModule v1.0.0

Exact navigationAdmin Area → Setup → Modules → Letter Manager → Activate

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

Run the portable installer, create module-owned tables and storage, then verify the three registered menu pages. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Upload the letter_manager directory to the CRM modules directory.
Open Admin Area → Setup → Modules.
Locate Letter Manager and select Activate.
Open Letter Manager → Dashboard, Templates and Settings.
Create a controlled test letter and verify the PDF, history row and public verification link.

Fields, choices and supported possibilities

Action scopeRun the portable installer, create module-owned tables and storage, then verify the three registered menu pages.

Module version1.0.0

Exact routeAdmin Area → Setup → Modules → Letter Manager → Activate

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

Activation includes install.php.
The installer creates or extends the history and template tables and creates uploads/letter_manager when absent.
A schema-version guard also runs during admin_init.

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.