SkieHow do I disable a user in Skie when a staff member leaves?
Open the users list, find the person and disable them. Their access to the dashboard stops, but their history stays in the audit log, so you can still see what they did. Disable rather than share a login, and do it the day someone leaves or changes role.
People move on, and device management access is the sort of thing that is easy to forget. A teacher who has left but can still open the dashboard is a risk to the school's data. Disabling is the quick fix.
Disabling a user turns off their access without deleting their record. That matters for two reasons. The audit log keeps showing who changed what, which is useful if you ever need to understand a past decision. And if the person returns, or moves to a different role, you can re-enable or invite them again at the new level.
Disabling a user does not touch any devices. Students' tablets keep following the rules of their group, and no one on those devices notices. The effect is limited to who can sign in to manage them.
Make it part of your leaving process. Add a line to your staff exit checklist: disable the Skie user, along with email and any other tools. If a person changes role, for example a teacher becoming a branch head, invite them in the new role and disable the old one rather than stretching one account across jobs.
As a broader safeguard, keep your number of organisation admins small, and review the users list each term. Anyone you cannot place should be disabled and re-invited if they turn out to be needed.
Practical tip: the audit log is your friend. After disabling someone, glance at their recent actions to confirm nothing unexpected happened.