PDF generation, branding and files

Understand PDF QR verification

Use the QR code to open the public verification URL tied to the letter unique code.

Audience: CRM staffPermission: Authenticated staff accountModule v1.0.0

Exact navigationOpen generated PDF → scan top-right QR code

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

Use the QR code to open the public verification URL tied to the letter unique code. 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 PDF.
Scan the QR code with a controlled device.
Confirm the URL uses letter_manager/verify/{unique_code}.
Verify the page shows the expected permitted fields and verification code.

Fields, choices and supported possibilities

Action scopeUse the QR code to open the public verification URL tied to the letter unique code.

Module version1.0.0

Exact routeOpen generated PDF → scan top-right QR code

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 QR uses QRCODE,L and the letter verify_url.
The QR link is public and does not require client login.

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.