SkieHow fast does a rule change reach managed devices?
For devices that are online, a rule change reaches them within seconds. For devices that are offline or switched off, it arrives at the next sync, which happens when the network returns or the screen turns on stale. Skie does not promise a specific figure, because it depends on connectivity.
When an admin publishes a change, whether it is a new app list, a changed schedule or a hardening switch, the signed policy bundle for the affected devices is updated. Devices that are connected pick it up quickly, apply it and read their protections back.
Devices that are not connected do not miss it. They keep running on the cached, signed rules they already hold. On reconnect, or when the screen turns on and the last sync is stale, they sync immediately and apply what is new. Retries cover weak connections.
Before you publish, use the impact preview. It shows which groups, devices and apps a change will touch, and the effective policy view shows the end result for a given device. Blocking beats allowing, and the most specific level wins, so a change at organisation level may be overridden below it. The where-used view helps when you change a shared policy or app list.
To confirm a change has landed, check the device page: the last-seen time should be recent and the compliance reading should include the new setting. You can also force a sync on a device or run a compliance check on demand.
Practical tip: for a time-critical change, such as extra apps for a single lesson applied to a whole class, make it a few minutes early and check that the group shows as on the latest policy in Insights before the lesson starts.