Open a QR public signing page
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Scan a valid QR and load the no-index, no-cache recipient page.
Where to goPublic action → Scan the QR code printed on a supported PDF
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
Scan a valid QR and load the no-index, no-cache recipient page. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Scan the QR code.
- Verify the displayed document and company context.
- If the record is pending, complete the signing form.
- If already signed, review the locked evidence page.
Fields and options
Action scopeScan a valid QR and load the no-index, no-cache recipient page.
Module version2.1.0
NavigationPublic action → Scan the QR code printed on a supported PDF
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- Invalid-format or unknown tokens return HTTP 404.
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.