SkieHow does Skie re-apply a protection if a setting is changed?
Skie checks each protection against the policy and puts it back if it has drifted. Rules are cached on the device and signed, so this works offline too. For example, if a user runs Reset all settings, the protections are re-applied within seconds. The change is then visible in the compliance score and the breach centre.
Skie holds the desired state of every protection as part of the signed policy bundle. The device accepts only bundles that verify, and it keeps the last good one cached. That cache is what makes re-applying possible without a network connection.
When something shifts, such as a setting that Android resets as part of a system action, the Skie app on the device notices the difference and applies the protection again. Skie runs as a background service with a watchdog worker, so a stopped process is restarted. The device also reports its presence regularly, about every four minutes, and syncs instantly when internet returns or the screen turns on after a stale period.
What the admin sees depends on how long the gap lasted. A protection fixed within seconds may only show as a brief dip. If a device stays out of contact longer than your Due or Overdue threshold, it appears in the breach centre, and you can sync and resolve it at device, group, branch, school or organisation level. All thresholds, including Offline unusual and Breach, are editable.
Re-applying is not the same as asking for permission. The student does not need to do anything, and there is no prompt to accept.
Practical tip: set the Due and Overdue thresholds to match how your devices are really used. A tablet that goes home for a long weekend should not look overdue on Monday.