How do I move a student to another group in Skie?

Students change class, hostel floor or batch during the year, and the dashboard needs to follow. Skie treats this as a change of place in the hierarchy, not as a new enrolment.

When you move a student, three things happen. They join the new group. The device is now governed by that group's policy and app list, and the effective policy view will show the result after all levels are combined. And the student's history and the device record stay attached.

Timing is straightforward. An online device picks the change up within seconds, and an offline one at its next sync. If you are moving students at a sensitive moment, such as the start of a lesson, force a sync or check that the group shows as on the latest policy.

There is no change to the seat. Seats are tied to a device and a student, and neither has changed. If the move goes the other way, for instance a student leaving the institution, the device is released through the lifecycle tools and the seat is freed.

Who can do it depends on role and scope. A branch head can move students between groups in their branch. A school admin can move between branches in their school. Moving across schools needs a higher level.

Skie moves students one by one or in bulk. For several at a time, see the bulk move entry. Students who must be added from scratch are enrolled by provisioning their devices, since bulk student upload is not available yet, and the team is working on it.

Practical tip: do moves before the change takes effect, not after, so the device already has the right rules on the first day.