Use the floating QR Compliance document button | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/use-the-floating-qr-compliance-document-button Publisher: Pixie Technologies LLC Admin records and audit Use the floating QR Compliance document button 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 open an existing compliance record from supported admin document pages. Audience: CRM staff; Permission: Administrator; Module v2.1.1; Where to goAdmin Area → Open supported invoice/payment/credit note/estimate/proposal → QR 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 Open an existing compliance record from supported admin document pages. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Go to a supported document page. - Select the floating QR Compliance button. - If the record exists, review it. - If warned that no record exists, generate the PDF first. Fields and options Action scopeOpen an existing compliance record from supported admin document pages. Module version2.1.0 NavigationAdmin Area → Open supported invoice/payment/credit note/estimate/proposal → QR Compliance EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - The injected button recognises supported admin URL/hash patterns. - It does not create the record; PDF generation does. 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 QR Code Compliance module overview (https://pixiecrm.com/help-centre/qr-code-compliance-module-overview)Review the QR event timeline (https://pixiecrm.com/help-centre/review-the-qr-event-timeline)Understand QR IP masking and location evidence (https://pixiecrm.com/help-centre/understand-qr-ip-masking-and-location-evidence)Export invoices and sales PDFs (https://pixiecrm.com/help-centre/export-invoices-and-sales-pdfs)Create a credit note (https://pixiecrm.com/help-centre/create-a-credit-note)