Geofencing and location policies
A site is a point plus a radius. A policy decides what happens with location when someone clocks.
| Mode | Check in / resume outside a site | Check out outside a site | Location stored |
|---|---|---|---|
On-site only (strict) |
Rejected | Recorded, flagged | Yes |
Location recorded (flexible) |
Recorded, flagged | Recorded, flagged | Yes |
Location off (off) |
Recorded | Recorded | No |
Other settings on a policy:
- Max GPS inaccuracy: fixes worse than this count as "location unavailable". The default is 150 m.
- Overtime rate: the default is 1.5×, under the Saudi Labor Law.
- Auto check-out: checks someone out after this many hours.
- Office Wi-Fi and selfie requirements: reserved for a later release.
Which policy applies?
Policies and shifts are attached through assignments. When more than one applies, the most specific one wins:
employee › department › site › company
Within the same scope, an assignment with dates beats an open-ended one. That is how a Ramadan schedule takes over automatically for its date range.
An employee with a home site is only checked against that site. An employee without one can use any of the company's sites.
Privacy
Omni reads location once, at the moment of a clock event, and only when the person's policy needs it. There is no background tracking. Under Location off, coordinates are never stored.