SkieHow is an organisation structured in Skie: school, branch, group, student and device?
Skie arranges everything in a tree: organisation, then school, then branch, then group, then student, then device. Rules, admins and reports attach to the level where they belong, and a student sits in a group with one device. This lets a trust, a franchise or a company manage hundreds of devices without treating them one by one.
At the top is the organisation, the customer account. Under it are schools, which could be the schools of a trust, the campuses of an institute or the divisions of a company. Under a school are branches, such as a site, a section or a franchise outlet. Under a branch are groups, typically a class, a batch, a hostel floor or a team. A student sits in a group and has one device.
Each level has a purpose. Policy and app lists are chosen at the group level, one policy and one app list per group, while settings that must apply everywhere can be set at organisation level. Admins are scoped to levels too, so a branch head sees their branch and a teacher sees their class. The breach centre and Insights roll up through the same levels, from device to group, branch, school and organisation.
You do not have to use every level. A single school may use one school, one branch and several groups. A company with departments can treat each department as a group, or as a branch if it needs its own head.
Rules flow down the tree, and the most specific level applies last. That is explained in the next entry. Moving students between groups, and promoting a whole group, change where a student sits without changing the device.
Practical tip: draw your structure on paper before setting it up, with a name for each level and who will own it. It is easier to start with fewer levels and add later than to untangle too many.