Public scanning and signing

Allow or refuse QR device geolocation

This guide explains the optional browser-location attempt and continued signing when it is unavailable. 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 → Submit signature
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

Understand the optional browser-location attempt and continued signing when it is unavailable. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.

Follow these steps

  1. Submit the completed form.
  2. When prompted, allow or refuse location according to policy.
  3. Wait for the signing request to continue.

Fields and options to review

Browser attemptLow-accuracy geolocation, maximum age 60 seconds, approximately 3.5-second timeout.
Stored device dataLatitude −90..90, longitude −180..180, accuracy 0..100000 and timezone up to 100 characters when valid.

Rules the system enforces

  • Signing continues when permission is refused or geolocation is unavailable.
  • Network headers may separately contribute country/region/city/postcode/ray metadata when supplied by infrastructure.

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.