Track apparatus and opted-in responders on private maps.
B.3 private tracking uses Active911-reported locations, department-level controls, individual responder consent, response-status gating, and short-lived operational display data.
Privacy model
Active911 device tracking is optional and private. Exact positions are used only on authenticated operational maps and the authorized StationCommand Home Respond API. They are not added to public displays/APIs, incident history, analytics, or persistent incident/location history.
Active911 permission
The Active911 token must include Read Devices / read_device. If device-location requests report that permission is missing, generate/authorize a replacement token with Read Devices and update the Refresh Token.
Department tracking controls
Administration → Integrations → Active911 Integration → Private Incident & EOC Maps — Active911 Device TrackingApparatus Tracking and Responder Tracking both default to Disabled. Choose a Location Refresh interval of 15, 30, or 60 seconds.
Apparatus tracking
- Import or create the Active911 device.
- Classify/link it as Apparatus.
- Enable Apparatus Tracking.
- Save Active911 Settings.
Eligible apparatus can appear on private incident/EOC maps whenever tracking is enabled; apparatus does not need RESP or ARRIV status.
Responder tracking
Responder tracking requires both the department switch and each member's personal opt-in.
Member Menu → My Settings → Active911 Location SharingA responder is eligible only when the linked device is RESP or ARRIV for the applicable incident. In EOC, the member must be RESP/ARRIV on at least one active EOC incident.
Members can choose Device/Admin Default or a personal map icon (Car, SUV, Pickup, Van/Utility, Fire Engine, Ladder, Ambulance/Rescue, Command Vehicle, Tanker/Tender, Utility) and optionally a color.
Marker freshness
| Position age | Display behavior |
|---|---|
| 0–2 minutes | Full configured color. |
| >2–30 minutes | Faded/transparent configured color. |
| >30 minutes | Gray/stale marker. |
StationCommand Home tracking
Home webhooks do not contain responder/apparatus coordinates. A signed webhook only indicates tracking availability. An authorized Home instance uses its Respond API bearer token to retrieve the current eligible positions.
This means a responder opt-out or Active911 status change takes effect on the next Home API refresh without copying exact coordinates into outbound webhook logs.
Troubleshooting a missing marker
- Confirm the Active911 token has Read Devices.
- Confirm the numeric Device ID is correct in StationCommand.
- For apparatus, confirm Apparatus classification and department Apparatus Tracking.
- For responders, confirm Responder Tracking, personal opt-in, linked device, and RESP/ARRIV status.
- Confirm Active911 has a recent location for the device.