Lone Worker

No. Location is captured only at trigger time — when an SOS is tapped. There is no continuous background GPS tracking, and a worker-raised floor issue skips geolocation entirely.

The alert climbs each roster tier as its acknowledgement timeout elapses. If the whole ladder is exhausted with no acknowledgement, a dead-man's switch broadcasts to your safety admins over push, email, SMS, and voice. That guarantee is deliberately not gated by any tenant toggle — an admin can't turn the break-glass off. The push and email follow each admin's own notification settings; the text and the phone call go out regardless, wherever texts and calls are on for the organization.

It's automatic. Timed "I'm safe" check-ins arm on their own for any worker on a covered shift — one where a responder roster resolves for the site or team — so there's nothing for the worker to set up. Cadence comes from a site/team check-in schedule or your tenant's defaults (60-minute interval, 10-minute grace, both admin-configurable). If a check-in is missed past its grace window, an alert auto-raises; no one has to watch a board and no worker has to remember.

Yes. A signed (HMAC) webhook accepts events from wearable/IoT devices — RFID badge presses, push-to-talk panic buttons, line sensors — and each raises an alert onto the same responder escalation, acknowledgement, and audit trail as a phone-raised SOS. Devices are attributed to a worker by badge ID, with a fallback user for unbadged sensor events. An admin connects a device platform under Admin → Integrations with a signing secret and gets the webhook URL to give the vendor. Device alerts are off until an admin turns on "Let wearable & IoT devices raise alerts" in Lone Worker settings, so connecting an integration never starts paging people by itself.

They're complementary. Lone Worker is the real-time engine — trigger (SOS, missed check-in, floor issue, wearable), escalate up the responder ladder, acknowledge, resolve — for someone who may be in danger right now. Safety Hub is where incidents live as durable records. When a responder resolves an alert as "incident" (a note is required), Lone Worker hands off and opens a Safety Hub incident automatically — typed as an equipment failure for a floor issue, otherwise a security incident. That handoff is on by default for tenants that use Safety Hub, and configurable per tenant.

Optionally. When the Live Assist app is turned on and you turn on "Open a live video channel to the responder when an alert is acknowledged" (off by default), acknowledging an alert — an SOS or any other — opens a live video channel to the worker so the responder can see the scene. Without Live Assist, escalation, acknowledgement, and resolution all work exactly the same — video is an add-on, not a dependency.

Yes, both OAuth-scoped. Workers get a safety API to read their status, trigger an SOS, raise a floor issue, and answer the current check-in (native-app parity with the mobile surface). Responders get an alerts API to list and read alerts, and to acknowledge, hand back and resolve them. Both run on the same escalation and audit machinery as the in-app surfaces.