SkieHow are Skie app updates verified, and can we hold one back?
The Skie app updates itself, and each update is checked with a checksum before it is installed. Releases roll out in stages to chosen organisations and can be paused. To roll back a bad update, pause it and stage the previous version. Students cannot trigger or block it.
A management app that can update itself is convenient, and also something to protect. If anyone could swap the update for another file, the device would be at risk. So updates carry a checksum that the device verifies before installing.
Rollouts are staged. The Skie owner releases a new version to chosen organisations first, then widens it. If a problem appears, the release can be paused, which stops it reaching further devices. This is how fixes for reported bypasses reach every device without anyone touching a tablet.
For you as a customer, the useful questions are about control. Can we hold an update for a week? Pausing or staging does that on the Skie side, and you can ask the team to include your organisation in a later stage. Can we roll back a bad update? Pause it and stage the previous one.
Check the result on the dashboard. The insights include a share of devices on the latest app and on the latest policy, so you can see how far a rollout has reached, and the compliance score tells you that protections stayed in place after.
Practical tip: during a pilot, ask to be in an early stage so you see changes first and can give feedback. Avoid planning an exam or a big event on the day a new stage is scheduled to reach you, and agree the timing with the team.