SkieWhat should we do if a student finds a way around a rule?
Report it to Skie support with the device, the steps and the date. The team looks into it and ships a fix as an update, which reaches every device, not just yours. Meanwhile the breach centre and compliance score help you find affected devices.
No protection design is finished, which is why the process after a report matters. Treat a student's discovery as useful information rather than only a problem to punish.
Start by gathering facts: the device and group, what the student did, what happened, and the time. Check the device's last seen time, its compliance score, and any breach centre entry. If the device read-back shows a protection off, you will see which one.
Send the details to support. The team reviews the report and fixes the cause. Because the Skie app updates itself with checksum verification and rolls out in stages to chosen organisations, a fix reaches every device after release, and an update can be paused if needed. You do not need to touch each tablet.
While waiting, reduce the exposure. If the issue involves an app, take it off the list or hide it from the group. If it relates to a setting, a stricter group policy or the panic lock for the affected group can bridge the gap. The impact preview shows what a change affects before you apply it.
Handle the student separately. School policy decides consequences. Skie's job is to keep the evidence tidy: the audit log records changes, and the breach centre records the event.