Who sees which alerts, and how are alerts routed by role?

In Skie, every device sits at the bottom of a structure: organisation, school, branch, group, student, device. People attach to one level of that structure through their role, and what they can see follows from it. This is the same idea that decides who can change a rule.

So routing is not a separate system you configure. The breach centre shows each person the alerts inside their part of the structure. A teacher with a class sees silent or out-of-zone devices in that class. A branch head sees the whole branch. The school admin sees the school, and the organisation admin sees the lot. If you want a warden to handle hostel alerts, give the warden the role and the group, and their view is the hostel.

Page access is also set per role. If location or the breach centre should not be visible to teachers, you can switch the page off for that role. Parents are read-only on school devices, and what they can see is for the school to decide.

One honest limit: alerts are shown in the dashboard. Email alerts, and notifying parents of an alert, are not available yet, and the team is working on both. That means someone has to look. The usual answer is a short morning check by the person at each level, as in the admin routine.

Practical tip: when you invite users, give each one the lowest level that lets them do their job. It keeps their alert list short and relevant.