SkieWho can see the data in Skie?
People see what their role allows. An organisation admin sees the whole organisation, a school admin sees their school, a branch head their branch, a teacher or class admin their group, and a parent sees their own child's device read-only. Skie staff can see data for support, as set out in your agreement.
Skie is built around a hierarchy: organisation, school, branch, group, student and device. Roles are tied to that hierarchy. The wider the role, the more of it the person sees. A class admin looks after one group. A school admin looks after the school. Nobody sees a branch they have not been given.
Parents on school-managed devices are read-only. They can see their own child's device, but they cannot change the organisation's rules. Page access can also be switched on or off per role, so an organisation can decide that teachers see devices but not locations, or that only certain roles see the audit log.
The audit log records who did what, which helps when an organisation needs to answer a question about a change. It is the practical counterpart to role-based access: permission is limited, and the record shows how it was used.
Skie's own owners and technicians can reach organisation data for support, and the terms for that belong in your agreement. That is covered separately in the entry on Skie staff access.
A practical tip: when you set up, give each person the narrowest role that lets them do their job, and review the list of invited users once a term. People change posts, and old access is the easiest privacy gap to close. The guide on role-based access walks through a sensible split.
- Access follows the hierarchy from organisation down to group
- Parents are read-only on school devices
- Page access can be switched per role
- The audit log records changes