The dashboard is the page you leave open: a live map of the active farm with the mob on it, four headline numbers, and the short list of alerts that actually need a person. Its heading is the farm’s name.
The dashboard: stat cards, overlay toggles, live map and needs-attention list

​
Headline numbers

Four stat cards across the top:
  • Open alerts — turns red when anything urgent (cast or distress) is open.
  • In progress — acknowledged but not yet resolved.
  • Resolved (24 h) — what the team has closed out today.
  • Sentinels reporting — GPS collars heard from recently.

​
The live map

The map shows the property boundary and fields, with a sheep marker per sentinel collar — green normally, red when that device has an unresolved alert. Click a marker for the device id, last fix time and battery voltage. Ear tags render as approximate presence around the sentinel that last heard them. Use the Overlays row to toggle layers: sentinels, ear tags, signal links, drone media capture points (when recent captures exist), the boundary, and each named field. The Signal links layer draws the live radio topology as dotted lines, coloured green / amber / red by link quality:
  • BLE (fine dots) — each ear tag to the collar(s) that can hear it, with the freshest RSSI measured during a scan window. Click a line for the reading, advert count and whether that collar is the tag’s current relay.
  • LoRa (long dashes) — each sentinel collar to the farm’s 📡 relay, using the last-uplink RSSI from the relay’s status heartbeat (also shown: WiFi RSSI and heartbeat age).
A relay has no GPS of its own, so the first time it reports it appears unplaced (dashed red border) at the map centre. An Admin drags the 📡 marker to the mast’s real location; the position is saved and the LoRa lines appear.
With the Realtime updates plan feature, positions and alerts push to the map the moment they land; otherwise the dashboard refreshes every 15 seconds.

​
Needs attention

Below the map, Needs attention lists the most recent unresolved alerts — device, kind, when (repeats collapse into one row with an occurrence count), status, and any automated actions already taken (webhook notified, drone launched). From here you can:
  • Acknowledge — tell the team you’ve seen it.
  • Resolve — open the guided resolve flow and record the outcome (see Alerts).
When everything is closed out the list reads “All quiet — no unresolved alerts.” — the state you want. Manage all alerts → takes you to the full Alerts page.