SkieOSRole-based access for school device management
In short
Role-based access gives each person a dashboard scoped to their level: teachers manage a class, section heads a branch, principals a school and owners everything. It speeds up change and limits exposure.
The levels
| Role | Typically manages |
|---|---|
| Teacher | Their class and its devices |
| Section head or HOD | All classes in their branch |
| Principal | The whole school |
| Organisation owner | Every school and branch |
| Hostel warden | Hostel groups and night mode |
Why it helps
- Teachers change apps for a lesson without raising a ticket
- Leaders see status across branches
- People cannot see or change what is not theirs
- Changes are recorded against a named person
How rules combine
Rules set at the top flow down. A branch or class can refine them within what the level above allows. The most specific level applies last, which keeps behaviour predictable.
Designing your roles
Start from how your organisation already works. Give people the lowest level that lets them do their job, and review access when staff change.
Frequently asked questions
Can a teacher see other classes?
No. A teacher's dashboard is scoped to their own class.
Can leadership see everything?
Owners and principals see the levels beneath them, according to their role.
Can access be changed?
Yes. Roles can be assigned and updated as staff change.