Operational summary
Geofences delimit areas for operations or access control. They are stored per organization and power the web map, dashboard alert logic, and the mobile app (sync and in-field notices).
A geofence is a delimited area on terrain with operational meaning: 'something different happens inside than outside'. They can be arbitrary polygons or point-centered circles, depending on real site geometry. Sentinel stores geofences per organization: each org owns its own and they don't mix with others.
Deep dive
The product distinguishes two variants and you must understand the difference before drawing. An operations zone is informational: it marks a working area, a coverage zone assigned to a team, a sector of tactical interest. It doesn't trigger alerts on its own; it adds context to the map and history. Useful so the operations center understands 'this unit is inside the north area' without reading raw coordinates.
A restricted zone, in contrast, is actionable: operator entry can generate a notification on their app and a highlighted event in the tactical log. Use it for sensitive perimeters: authorized-personnel-only areas, hazardous zones requiring special PPE, borders not to be crossed in specific operations. The idea is that both the field person and the operations center are informed simultaneously.
The choice criterion is simple: do I need something to happen when a unit crosses the border, or do I just need to see the zone on the map? The first is restricted; the second is operations. Mixing them is usually a mistake: 'decorative restricted' generate log noise, 'operations that should alert' get missed when needed. Rename zones with clear operational criteria so log and app messages are self-explanatory.
Key takeaways
- Operations: working area or tactical interest (visibility and map context).
- Restricted: area where operator entry should raise a notice (mobile notification and monitoring from the operations center).
Open in product