Setup, version, access and architecture

Deactivate or remove Letter Manager safely

Preserve required correspondence evidence before disabling or manually removing the module.

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

Exact navigationAdmin Area → Setup → Modules → 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

Preserve required correspondence evidence before disabling or manually removing the module. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Inventory letters, PDFs, signatures, enclosures and open-event evidence that must be retained.
Deactivate through Setup → Modules.
Verify the Letter Manager menus and hooks no longer load.
Do not drop tables or delete uploads unless an authorised retention process explicitly requires it.
Re-enable and test if the change was intended to be temporary.

Fields, choices and supported possibilities

Action scopePreserve required correspondence evidence before disabling or manually removing the module.

Module version1.0.0

Exact routeAdmin Area → Setup → Modules → 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 supplied module registers activation but no deactivation or uninstall cleanup hook.
Routine deactivation should not delete module data.

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.