Understand QR document fingerprint
Follow this guide to use the SHA-256 snapshot fingerprint as part of later integrity verification. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → QR Compliance Records → Open signed record → Cryptographic evidence
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 you’ll accomplish
Use the SHA-256 snapshot fingerprint as part of later integrity verification. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to the record.
- Check Document fingerprint.
- Verify the integrity panel passes after signing.
Fields and options to review
Action scopeUse the SHA-256 snapshot fingerprint as part of later integrity verification.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open signed record → Cryptographic evidence
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The fingerprint is calculated from the stored snapshot, not from a future live document view.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.