Who can see what on the Skie dashboard in a school?
Each person sees only their own level. An organisation admin sees every school, a school admin sees one school, a branch head sees one branch, a teacher sees their own group, and a parent sees read-only status for their own child. Page access can also be switched on or off per role.
Skie ties access to the same structure as the school: organisation, school, branch, group, student, device. The role you are given decides which level you start at, and you cannot see anything above or beside it. A Class 8B teacher does not see Class 9A. A branch head does not see the next branch.
The main roles are organisation admin, school admin, branch or section head, class admin or teacher, and parent. Skie's own owner and technician roles exist for support, and your agreement should say how that access is used. Parents are read-only on school devices, so they can look but cannot change anything.
On top of the level, page access can be switched per role. That matters most for location. A school might let branch heads and the hostel warden see where devices are, keep it hidden from class teachers, and give parents status only. You make that call once and it applies to everyone in the role.
Everything a person can do is also limited by what they can see. A teacher can lock their group or give it an extra app for a lesson, but cannot edit the school's baseline policy. Locked settings from head office stay locked.
A practical tip: write down your roles on paper first, with who should see location, who may change policies and who may only view. Then invite users one level at a time and check the dashboard as each role before you go live.