SkieThe best way to manage student tablets across many branches
The best way to manage student tablets across many branches is one central MDM with a hierarchy: organisation rules at the top, branch and class rules below, and local heads who control only their own devices. Use one enrolment process everywhere and watch compliance from a single alerts view.
Why many branches break flat setups
With one school and a hundred tablets, a single administrator can cope. Add four branches and the same approach produces four versions of the rules, three different ways of enrolling a device and nobody who can say how many tablets are healthy today.
The fix is structure, not more effort. A branch is a level in the system, not a separate tool.
Build the hierarchy first
Create levels that match reality: organisation, school, branch, group, student, device. Set the rules that must be identical everywhere at the top, such as blocking factory reset and VPN apps. Let each branch or class change only what you allow. The most specific level applies last, and blocking beats allowing, so a branch cannot accidentally reopen something the organisation closed.
Before any change reaches devices, preview it. An impact preview shows how many devices a change will touch, which is the difference between a safe edit and a morning of calls.
Decide who can do what
| Role | Typical scope | Typical task |
|---|---|---|
| Organisation admin | Every branch | Set global rules, review compliance |
| School admin | One school | Manage branches and policies |
| Branch or section head | One branch | Enrol devices, handle replacements |
| Class admin or teacher | One class | Open an extra app for a lesson |
| Parent | Own child, read-only on school devices | See status and location where enabled |
Make enrolment boring and identical
Use the same steps at every branch: reset, enrol into a group, confirm the rules applied, label the device. A native provisioning app and a one-time enrolment token per device keep the process repeatable, and a readiness check before provisioning catches devices that are not ready. The detail is in How to provision Android devices at scale.
Identity recognition by IMEI or serial matters across branches. A tablet that is reset and re-enrolled should not take a second licence seat.
Watch the whole network from one place
- A single alerts view across all levels, with sync and resolve at device, group, branch, school and organisation level
- Last seen times, so a missing check-in is treated as a problem, not silence
- A compliance score read back from each device after every rule change
- Daily snapshots per group, so a branch that falls behind stands out
Handle moves and replacements without rework
Students change sections and tablets break. Moving students singly or in bulk, promoting a whole group at year end and replacing a device while keeping the student, group and history are everyday operations at this scale. If each one needs a support ticket, the system will not hold up. See Lost or stolen managed tablet for the loss case.
Where Skie fits
Skie for Enterprise was designed for this shape, with seat-based licences, one device per seat, and the owner able to freeze an organisation or lock all devices at once. Bulk student upload is not available yet, though students can be moved in bulk once they exist. The team is working on it.
Frequently asked questions
How do schools manage student tablets across several locations?
They use one MDM with a hierarchy of organisation, branch and group. Global rules are set once at the top, and each branch head manages only their own devices.
Can each branch have different apps?
Yes. Rules flow down from the organisation, and a branch or class can add or remove apps within what the higher level allows.
How do we manage 100 student tablets with a small team?
Use groups, role-based logins for teachers and an alerts view, so routine changes happen at class level and IT only sees real problems.
What if one branch has poor internet?
Rules are cached on the device and keep working offline. Devices sync again when the connection returns, and long silence is flagged as a breach.
How do we keep branches consistent?
Set non-negotiable rules at organisation level, use the same enrolment steps everywhere and review the compliance score per branch.