Understand PDF QR verification
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use the QR code to open the public verification URL tied to the letter unique code.
Where to goOpen generated PDF → scan top-right QR code
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 this guide helps you do
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.
Follow these steps
- Go to the PDF.
- Scan the QR code with a controlled device.
- Verify the URL uses letter_manager/verify/{unique_code}.
- Check the page shows the expected permitted fields and verification code.
Fields and options
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.
Rules and limits
- The QR uses QRCODE,L and the letter verify_url.
- The QR link is public and does not require client login.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.