The unit page's "Who is contacted" panel shows the effective list for that one unit: the people routed by role and territory (managed on the People page — that is the only place they are edited), plus any extra unit-only contacts. Those extras, set in the unit's Settings, are additive — an address or number with no account behind it, like a kitchen phone. They are never copied from the People page and editing them changes nothing there; a person who appears through both paths is contacted once.
When a unit crosses a threshold, the recipients are worked out from the store it's assigned to — which is why an unassigned unit alerts nobody.
- Contacts attached to that store who have asked for this level.
- Members whose territory covers the store — directly, by region, by market, or through active temporary coverage — filtered by their role's policy and their own preferences.
- Anyone the same person would appear as twice is contacted once. A store contact who is also a member doesn't get two texts.
- If nobody acknowledges within the first escalation step's delay, the chain begins.
Where escalation chains conflict, the most specific wins: rules on the unit itself, then an override on the store, then the organization's default chain.
In the dashboard: Readiness — Answers one question for your whole fleet: if a store hit Danger right now, would a human find out?