Configure QR Code Compliance general settings
Follow this guide to set the master compliance, verified-stamp and public-IP behaviour. 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.
Where to goAdmin Area → Setup → Settings → QR Code Compliance → General
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
Set the master compliance, verified-stamp and public-IP behaviour. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Set Compliance enabled to Yes for public signing records.
- Set Verified stamp enabled according to the PDF evidence requirement.
- Set Show full public IP according to privacy policy.
- Save settings.
Fields and options to review
Action scopeSet the master compliance, verified-stamp and public-IP behaviour.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → General
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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.