Security, privacy, limitations and troubleshooting

Troubleshoot a missing Letter Manager menu

Restore activation, file loading or session access without changing unrelated modules.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

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

Restore activation, file loading or session access without changing unrelated modules. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm Letter Manager is active.
Confirm letter_manager.php and hooks files are present and readable.
Check PHP syntax and the CRM application log.
Load an admin page to run the schema guard.
Reopen the sidebar.

Fields, choices and supported possibilities

Action scopeRestore activation, file loading or session access without changing unrelated modules.

Module version1.0.0

Exact routeAdmin Area → Setup → Modules; server → 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 sidebar is registered on admin_init.
Missing or fatal hook files can prevent menu registration.

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.