E-signature and public verification

Understand public verification email masking

Interpret the partially masked email shown for delivery evidence.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationPublic verify page → Email delivery

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

Interpret the partially masked email shown for delivery evidence. These instructions follow the inspected module’s live hook, route, controller, model, installer, PDF helper and view flow.

Exact step-by-step process

Confirm the displayed local part is masked.
Confirm the domain remains visible.
Use internal view for the full authorised address.

Fields, choices and supported possibilities

Action scopeInterpret the partially masked email shown for delivery evidence.

Module version1.0.0

Exact routePublic verify page → Email delivery

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

mask_email preserves the domain and reveals portions of the local part based on its length.
Masking reduces exposure but does not anonymise the domain or guarantee the person cannot be inferred.

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.