Understand QR Code Compliance routes
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 supported admin, document lookup and public signing endpoints through their normal links.
Where to goCode-backed reference → qrcode controllers and helper URLs
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What this guide helps you do
Use the supported admin, document lookup and public signing endpoints through their normal links. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Use QR Compliance Records for admin list/detail access.
- Use the floating document button where available.
- Use the QR-generated public URL for recipient signing.
Fields and options
Action scopeUse the supported admin, document lookup and public signing endpoints through their normal links.
Module version2.1.0
NavigationCode-backed reference → qrcode controllers and helper URLs
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- Public signing uses qrcode/qr_sign/index/{64_hex_token}.
- The admin document lookup accepts only invoice, payment, credit_note, estimate and proposal plus a positive ID.
Check it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Related guides
Was this guide useful?Your response is stored only in this browser.