Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
E-signature and public verification

Understand public verification email masking

Interpret the partially masked email shown for delivery evidence. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0
Jump to steps
Where to goPublic verify page → Email delivery
Before you start
  • 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 you’ll accomplish

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.

Follow these steps

  1. Verify the displayed local part is masked.
  2. Verify the domain remains visible.
  3. Use internal view for the full authorised address.

Fields and options to review

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.

Rules the system enforces

  • 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.

How to confirm it worked

  • 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.
Letter Manager module overviewUnderstand default public verification fieldsUnderstand non-configurable public verification elementsHandle invalid verification or signature linksUnderstand Letter Manager public token and hash securityUnderstand Letter Manager signature validation limitationsConfigure SMTP email deliveryAdd and manage customer contactsClient portal overview