Understand QR IP masking and location evidence
Distinguish full/masked IP, network location headers and optional device coordinates.
Where to goAdmin Area → QR Compliance Records → Open 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 this guide helps you do
Distinguish full/masked IP, network location headers and optional device coordinates. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Check first-scan and signed IP values.
- Check network and device location blocks.
- Apply the public full-IP setting when checking the public page/PDF.
Fields and options
Action scopeDistinguish full/masked IP, network location headers and optional device coordinates.
Module version2.1.0
NavigationAdmin Area → QR Compliance Records → Open record
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- Infrastructure-provided location is not independently geocoded by this module; treat it as supplied network evidence.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.