Scan a QR code and an operator is on your server. From there Beacon relays their position to the TAK picture on a heartbeat you set, in the background, with the phone locked. It holds onto what it cannot send until the signal comes back.
Three steps, and the third one is the only one anybody else sees.
The operator scans an enrollment QR code from your EOTAK dashboard or EOTAK Stack app and gets a short-lived session in return. No account, no certificate bundle, nothing typed in.
Beacon sends GPS heartbeats at an interval you set, through your server rather than straight at the network.
Each validated heartbeat becomes a Cursor on Target event on your TAK server. ATAK, iTAK and TAK Aware clients all see the operator as a live marker.
Five things it was built to do, and nothing it was not.
Beacon never talks to TAK infrastructure directly. Enrollment and every heartbeat go through your EOTAK Server, which validates the session and posts the position on, so the secrets stay off the phone in somebody’s pocket.