SkieIs there a maximum time for offline mode, and who sets it?
Yes. Offline mode has an organisation-level maximum, set by the organisation admin, that caps how long any device can stay in it. This is how an organisation limits offline hours. Skie does not publish a default length, so choose one that matches how your teams really work.
Offline mode is meant for a gap you expect, not for an open-ended exemption. To stop it being used that way, the organisation sets a maximum duration. The setting lives at organisation level, so a school admin or branch head cannot quietly extend it for their own group.
When choosing the maximum, start from the longest legitimate absence from connectivity. A logistics driver on a multi-day route needs a longer cap than a teacher with a half-day trip. Skie does not suggest figures here because the right answer is specific to your work.
What happens at the limit: offline mode ends and the device returns to normal sync behaviour. It will try to reach the server, and the unlock gate applies if the last sync is older than the Due limit. This is covered in the how offline mode ends entry.
What stays the same during offline mode: the cached, signed rules and all hardening continue to be enforced. The cap limits the time the offline app set is in play, not the protections.
Someone asking whether Skie can limit offline hours for a team is really asking about this setting. The answer is yes, in the sense that you cap the duration of offline mode, and also set the Due, Overdue, Offline unusual and Breach thresholds so unexpected silence is flagged.
Practical tip: write the cap into your device policy so staff know it exists, and review it after a month of real use.