Handle a QR record that is already signed
Follow this guide to review rather than replace a locked signature. 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 goPublic QR page → Signed 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
Review rather than replace a locked signature. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Go to the QR URL.
- Check the locked evidence.
- Do not attempt to submit a second signer.
- Create a new source document where a separate signature is legally required.
Fields and options to review
Action scopeCheck rather than replace a locked signature.
Module version2.1.0
NavigationPublic QR page → Signed record
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- POST requests against a signed record redirect to the same public record.
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.