Admin records and audit

Use QR source-document and public links

Follow this guide to open the underlying CRM document or its public evidence from the record detail. 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
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

Open the underlying CRM document or its public evidence from the record detail. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Select Open source document to return to the supported sales record.
  2. Select Open public record to view the same recipient-facing URL.
  3. Verify IDs and document number match.

Fields and options to review

Action scopeOpen the underlying CRM document or its public evidence from the record detail.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open record
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

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

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.