Admin records and audit

Review a QR Compliance record

Inspect source document, client, recipient, signature, scan/sign metadata and integrity.

Audience: CRM staffPermission: AdministratorModule v2.1.1
Exact navigationAdmin Area → QR Compliance Records → Open record
Before you begin
  • 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 covers

Inspect source document, client, recipient, signature, scan/sign metadata and integrity. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Exact step-by-step process

  1. Open the record.
  2. Review document details and immutable snapshot.
  3. Review recipient-captured identity and declaration.
  4. Review signature, first scan, sign IP/browser/location and cryptographic evidence.
  5. Review the event timeline.

Fields, choices and supported possibilities

Action scopeInspect source document, client, recipient, signature, scan/sign metadata and integrity.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open record
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.

Code-backed validations and workflow rules

  • Only values and transitions exposed by the supplied module code are supported.
  • Server-side validation remains authoritative even when browser controls appear to accept a value.

Expected result and verification

  • 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.