Record creation, snapshots and PDF output

Understand QR snapshot secret redaction

Confirm security-like keys are replaced before snapshot storage. 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.

Audience: CRM staffPermission: AdministratorModule v2.1.1
Jump to steps
Where to goAdmin Area → QR Compliance Records → Open record → 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 you’ll accomplish

Confirm security-like keys are replaced before snapshot storage. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Go to the immutable snapshot.
  2. Verify credential-like values are not displayed.
  3. Report any unexpected sensitive field through the authorised security process.

Fields and options to review

Action scopeVerify security-like keys are replaced before snapshot storage.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open record → Snapshot
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Keys matching password, passwd, secret, token, API/private/encryption/remember/reset/verification key or hash patterns are stored as [REDACTED].

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.