Understand QR Code Compliance limitations
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 only the capabilities present in version 2.1.0.
Where to goAdmin Area → QR Compliance Records / Setup → Settings → QR Code Compliance
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 only the capabilities present in version 2.1.0. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Use PDFs to create records.
- Use the public URL for one-time signing.
- Use admin records for review and regenerate PDFs for stamps.
Fields and options
Action scopeUse only the capabilities present in version 2.1.0.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records / Setup → Settings → QR Code Compliance
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- No email notification/resend, expiry, revocation, token rotation, manual create/delete, API, webhook, cron, CSV export or bulk report is implemented.
- Expense QR integration is not live.
- Only administrators can use the records controller.
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.
Important code-backed limitationDeactivation and uninstall are destructive in this release; preserve required evidence before either action.
Related guides
Was this guide useful?Your response is stored only in this browser.