SkieWhat roles exist in Skie and who can do what?
Skie has seven roles: Skie owner and technician, organisation admin, school admin, branch or section head (a head of department), class admin or teacher, and parent, who is read-only on school devices. Each role works at its own level of the structure, and page access can be switched on or off per role.
The roles follow the hierarchy. The Skie owner and technician are the Skie team and look after the platform: granting seats, curating the filter list, approving apps. Inside a customer, the organisation admin has the widest view, then the school admin, then the branch head or HOD, then the class admin or teacher. A parent can look at their child's school device but not change it.
Scope matters as much as role. A school admin acts within their school, a branch head within their branch, and a teacher within their class or group. Reports, the breach centre and Insights show what is below the person's level, not more.
Within a role, the organisation can switch page access on or off, for example hiding the location pages from teachers. This is how you apply the principle that people should see only what their job needs.
The following entries cover each role in more detail, along with inviting and disabling users. The role names are fixed, so what you tune is scope and page access, not new custom roles.
A note on competitors: tools aimed at schools such as Lightspeed, GoGuardian and Securly are centred on filtering and classroom monitoring, while Skie is device-owner management with an institute hierarchy and bulk control. The role model above is part of that.
Practical tip: start with fewer admins than you think you need. Give teachers class-level access, and add higher roles only when a real task requires them.