Public scanning and signing

Open a QR public signing page

Scan a valid QR and load the no-index, no-cache recipient page. 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: Authorised document recipientPermission: Valid public tokenModule v2.1.1
Jump to steps
Where to goPublic action → Scan the QR code printed on a supported PDF
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

Scan a valid QR and load the no-index, no-cache recipient page. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Scan the QR code.
  2. Verify the displayed document and company context.
  3. If the record is pending, complete the signing form.
  4. If already signed, review the locked evidence page.

Fields and options to review

Action scopeScan a valid QR and load the no-index, no-cache recipient page.
Module version2.1.0
NavigationPublic action → Scan the QR code printed on a supported PDF
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • Invalid-format or unknown tokens return HTTP 404.

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.