SkieWhat does freezing an organisation do in Skie?
Freezing an organisation blocks new provisioning, so no more devices can be enrolled until it is unfrozen. Devices already enrolled keep their rules. It is used when you suspect misuse, such as someone trying to enrol devices they should not, or when you need a pause while you review.
Enrolment is the moment a device joins your organisation, and it is worth being able to close that door quickly. The freeze switch does exactly that.
When an organisation is frozen, provisioning stops. A new device cannot be enrolled, even if you have free seats and a valid licence. Devices already enrolled are not changed: their cached, signed rules continue, hardening stays on, and the dashboard works as before. It is a gate on new devices, not a lock on existing ones.
Typical reasons: a provisioning token may have been misused, a staff member has left on bad terms, you are mid-audit, or you want to hold new enrolments during a restructure. Freezing is fast and reversible, so it is a sensible first step when in doubt.
Do not confuse it with locking all devices, which is a separate action that locks the screens of enrolled devices at once. Freeze is about who can join. Lock is about what existing devices can do right now. Both sit at the organisation level.
Enrolment tokens are one-time and fetched automatically per device, and the model and licence are checked at provisioning, which already narrows the risk. Freezing adds a stop on top when you want one.
Practical tip: decide who may freeze and who may unfreeze, and write it into your policy. Then you will not be working that out in the middle of an incident.