E-signature and public verification

Configure public Letter Manager verification fields

Choose which recipient, delivery and signature details appear on public verification.

Audience: CRM staffPermission: AdministratorModule v1.0.0

Exact navigationAdmin Area → Letter Manager → Settings → Public Verification Fields

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

Choose which recipient, delivery and signature details appear on public verification. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Open Settings.
Select or clear each approved field.
Save Settings.
Open a controlled verify URL in a signed-out browser.
Confirm only the intended configurable fields are present.

Fields, choices and supported possibilities

Letter Reference NumberShows reference_no.

Letter SubjectShows subject.

Issue / Created DateShows date_created.

Recipient NameShows person/primary contact.

Recipient CompanyShows customer or external company.

Recipient EmailShows/masks delivery or recipient email where rendered.

Recipient PhoneShows external phone where rendered.

Recipient AddressShows external address where rendered.

Email Delivery DetailsShows send status, masked target and date.

Postal Delivery DetailsShows postal status and related details.

Signature / Acceptance DetailsShows signature image, signer, date and IP.

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.