Security, privacy, limitations and troubleshooting

Troubleshoot public letter verification

Resolve 404, missing fields, broken signature images or stale public settings.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Sent Letters History → Verify; Settings

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

Resolve 404, missing fields, broken signature images or stale public settings. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open Verify from the staff history to avoid mistyped codes.
If 404, confirm the history row and unique_code.
If fields are absent, review Public Verification Fields.
If signature image is broken, confirm the hash-based PNG exists.
Test in a signed-out browser.

Fields, choices and supported possibilities

Action scopeResolve 404, missing fields, broken signature images or stale public settings.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Verify; Settings

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

Only the values and actions exposed by the supplied Letter Manager v1.0.0 code are supported.
Browser controls are not a substitute for server-side and operational verification.

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.