E-signature and public verification

Understand Letter Manager signature evidence

Review the stored image and signer metadata after acceptance.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Sent Letters History → Internal Full View / Verify

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

Review the stored image and signer metadata after acceptance. 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 letter.
Review the signature image.
Review signer first name, last name and email.
Review acceptance date/time and IP address.
Compare the reference and content with the issued PDF.

Fields, choices and supported possibilities

Action scopeReview the stored image and signer metadata after acceptance.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → Sent Letters History → Internal Full View / Verify

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 signature filename is {hash}_signature.png.
acceptance_date is the server time at submission.
acceptance_ip is the CodeIgniter input IP address.

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.