Docs Company Admin Guide Public Site Info Page (Kiosk URL)

Company Admin Guide

Public Site Info Page (Kiosk URL)

Share-able URL with auto-refreshing check-in QR for tablets at the gate or worker WhatsApp groups.

Each site can publish an unauthenticated info page at /public/site/<token>/. Two main uses:

  • Tablet kiosk at the gate — leave a tablet open to the URL; workers walk up and scan the QR with their phones to check in or out.
  • Share-able link — paste the URL into a WhatsApp/SMS group; any worker who needs to check in opens it on their phone and scans, or taps the fallback "Open check-in page" button.

Enabling

On the Site Detail page, scroll to the Public Info Page card. Click Enable public info page. The card immediately shows:

  • The full URL with copy + open buttons
  • Disable — stops serving the page (URL is preserved if you re-enable later)
  • Regenerate URL — rotates the token; the old link stops working immediately. Use this if the URL leaks somewhere it shouldn't be.

Site managers can see the URL on Site Detail; only super-admins and admins can flip the toggle.

What's on the page

Site name, address, status, start date, expected end date, "View on map" link, your company name, and the assigned site managers (name + email only — no worker PII). Plus the live, auto-refreshing QR.

Refresh interval (default 15 min)

Configurable per site on the site edit form under the Public Info Page fieldset. Choices: 1, 2, 5, 10, 15, 30, or 60 minutes.

  • Shorter = more secure (a screenshot of the QR expires faster) but more bandwidth and more screen-flicker on tablets.
  • Longer = friendlier on tablets and battery, but a captured QR stays scannable longer.

15 min is a sensible default for most sites.

Pausing the site = kiosk offline

If the site's status is paused, completed, or archived, the public page returns a friendly "site unavailable" message instead of the QR. So pausing a site automatically takes the kiosk offline — no extra step needed.

Security

The URL contains a 128-bit random token. Disabling AND regenerating both work — disable preserves the token (re-enable later restores the same URL); regenerate creates a new token (old URL stops immediately). Every enable / disable / regenerate is logged to the activity log naming who did it.

Was this helpful?

Last updated: May 3, 2026