SkieCan one hostel with many blocks and floors be managed in Skie?
Yes. Treat the hostel as a school, each block as a branch and each floor as a group. Rules set for the whole hostel flow down, each floor can have its own schedule or app list, and wardens see only their own block. Insights then compares blocks without separate reports.
Large hostels are really several small ones. A boys block and a girls block, junior and senior floors, a separate wing for competitive exam students. Skie's structure gives you levels that fit: the hostel under an organisation, each block as a branch and each floor or wing as a group.
Rules flow down. A hostel-wide policy can carry the things that never change, such as blocking uninstall, the web filter, and the always-blocked VPN and browser lists. A floor can then add its own night window or app list. The most specific level applies last, and locked settings from above cannot be undone below.
The reason to use groups for floors is that groups carry one policy and one app list each. A junior floor with an earlier lights-out gets its own window and the senior floor gets another, with no per-student editing. Moving a student between floors is a single move, and if a whole floor changes rooms, you can move several students by selecting them.
Wardens and floor monitors can be scoped. A block warden sees one block. A floor supervisor with a class admin style role sees one floor. Page access can differ by role, so location can stay with the senior warden.
Insights and the breach centre roll up across levels, so the chief warden can see which block has the most silent devices or the lowest compliance and call that block's warden first.
A practical tip: model the structure on how people already talk about the hostel. If everyone says A block second floor, name the group that. Names that match daily speech make the dashboard much easier for new wardens to read.