Public scanning and signing

Accept the QR electronic-signature declaration

Provide the exact consent required to create a binding locked receipt. 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: Staff loginModule v2.1.1
Jump to steps
Where to goPublic QR page → Electronic-signature declaration
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

Provide the exact consent required to create a binding locked receipt. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Read the declaration.
  2. Verify that you are authorised, the displayed details are correct and the signature is intended to create a binding locked record.
  3. Select the consent checkbox.
  4. Submit.

Fields and options to review

Action scopeProvide the exact consent required to create a binding locked receipt.
Module version2.1.0
NavigationPublic QR page → Electronic-signature declaration
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.

Rules the system enforces

  • The server requires consent value 1 and stores the fixed declaration text with the evidence.

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.