Understand first QR scan evidence
Know what is captured when the public URL is first accessed.
Exact navigationPublic QR page → First valid access
Before you begin
- 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 this guide covers
Know what is captured when the public URL is first accessed. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Exact step-by-step process
- Open the public page.
- Afterwards, an administrator opens QR Compliance Records → record detail.
- Review first scan time, IP, location payload and user agent.
Fields, choices and supported possibilities
Action scopeKnow what is captured when the public URL is first accessed.
Module version2.1.0
NavigationPublic QR page → First valid access
EvidenceConfirm the stored record, status, output, email, event or log produced by the code path.
Code-backed validations and workflow rules
- Every access increments view_count and updates last_viewed_at.
- The first access stores first-scan evidence and inserts a first_scan event.
Expected result and verification
- 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.