E-signature and public verification

Open a stored Letter Manager signature image

Use the module’s public image endpoint from a signed verification or internal view.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationSigned letter → Verify/Internal Full View → signature image

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

Use the module’s public image endpoint from a signed verification or internal view. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open the signed record.
Confirm the image loads.
If it does not, verify uploads/letter_manager/{hash}_signature.png exists and is readable.
Do not substitute an unrelated image.

Fields, choices and supported possibilities

Action scopeUse the module’s public image endpoint from a signed verification or internal view.

Module version1.0.0

Exact routeSigned letter → Verify/Internal Full View → signature image

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

show_image({hash}) reads the expected PNG and returns image/png.
Missing files return HTTP 404.

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.