SkieHow does Skie recognise a device that has been reset, and does it use a second seat?
Skie matches a device by its IMEI or serial number, so a reset device that comes back is recognised as the same one and does not take a second seat. Android's Factory Reset Protection also asks a wiped device for the Skie organisation's Google sign-in, which only Skie holds.
A device can end up wiped for innocent reasons, such as a repair, or because someone tried to reset it. Either way, two questions follow: what does the dashboard do with it, and what can the person holding it do with it?
On the first, Skie uses the device identity, the IMEI or serial number, to recognise it when it is set up again. It is treated as the same device, so it does not consume a second seat. The licence count stays honest, and the history stays attached to the right student and group.
On the second, Skie blocks factory reset from Settings, and Factory Reset Protection is tied to the Skie admin account. A device wiped by some other route, for example from the recovery menu, asks for the organisation's Google sign-in before it can be set up again. Only Skie holds it, so a reset device is of no use to whoever took it. We do not call this impossible to get around; we say it is built to be tamper-proof, and that if anything ever did get through, the admin is alerted immediately, down to the exact device.
To bring a legitimately reset device back, it has to be set up again through provisioning. The model and licence are checked at that point, and the device is enrolled with a new one-time token.
Practical tip: if a device vanishes from the dashboard after repair, look for it as a new enrolment with the same serial before adding seats.