SkieWhat can a school admin do in Skie?
A school admin manages one school inside the organisation. They look after the branches and groups in that school, choose policies and app lists for those groups, invite and disable users at their level, move students, and see reports and the breach centre for their school only. They cannot change settings the organisation has locked.
In a trust or an institute with several campuses, each school usually has its own administrator. The school admin role gives them control of their school without giving them the whole organisation.
Typical work: setting up groups for the new year, assigning a policy and an app list to each group, adjusting schedules such as school hours, a study block and a break, and inviting branch heads and teachers. They move students between groups and can promote a whole group at the year end. They can sync and resolve items in the breach centre at the school level.
Limits come from two directions. Upward, they cannot see other schools, and organisation-level locked settings stay locked. Downward, they delegate: branch heads and teachers see only their part. Which pages each role can open is set by the organisation, so a school admin may or may not see location pages depending on how your organisation set it.
A practical point about the web filter. The Skie owner curates the list of filters, an organisation admin chooses from it, and a group can override with its own choice where the organisation allows. The default for organisations without their own is CleanBrowsing Family.
Compared with tools such as Google Family Link, which is a family tool, this is the institute side of Skie: a hierarchy with scoped admins and bulk control.
Practical tip: do the year-start set-up in order: groups, policy and app list per group, then students, then seats check.