Understand QR document and client snapshots | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-qr-document-and-client-snapshots Publisher: Pixie Technologies LLC Record creation, snapshots and PDF output Understand QR document and client snapshots Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. This guide explains that the immutable evidence copied at record creation. Audience: CRM staff; Permission: Administrator; Module v2.1.1; Where to goAdmin Area → QR Compliance Records → Open record → Document snapshot 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 Know the immutable evidence copied at record creation. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow. Follow these steps - Generate the source PDF to create the record. - Go to the record. - Check document, client and primary-contact snapshot data. Fields and options Action scopeKnow the immutable evidence copied at record creation. Module version2.1.0 NavigationAdmin Area → QR Compliance Records → Open record → Document snapshot EvidenceVerify the stored record, status, output, email, event or log produced by the code path. Rules and limits - Payment snapshots include the related invoice and use that invoice for client/currency context. - Proposal client context is used only when rel_type is customer; otherwise client ID is zero. 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)Understand supported QR document types (https://pixiecrm.com/help-centre/understand-supported-qr-document-types)Understand QR snapshot secret redaction (https://pixiecrm.com/help-centre/understand-qr-snapshot-secret-redaction)Understand QR public token generation (https://pixiecrm.com/help-centre/understand-qr-public-token-generation)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)