Setup, version, access and architecture

Open Letter Manager Settings

Choose which stored details are exposed on public verification pages.

Audience: CRM staffPermission: AdministratorModule v1.0.0

Exact navigationAdmin Area → Letter Manager → 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

Choose which stored details are exposed on public verification pages. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Sign in as an administrator.
Open Letter Manager → Settings.
Review Public Verification Fields.
Select only the fields approved for public display.
Save Settings and test a public verify link.

Fields, choices and supported possibilities

Action scopeChoose which stored details are exposed on public verification pages.

Module version1.0.0

Exact routeAdmin Area → Letter Manager → 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

The settings controller explicitly denies non-administrators.
The settings affect only the public verification page; internal staff and client-side views are not filtered by these selections.

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.