SkieWhat is a provisioning session in Skie?
A provisioning session is a run of provisioning tied to one group. You open a session for the group, set up devices into it one after another, and the dashboard shows which students are done and which are waiting. It keeps a classroom rollout organised and ties each device to the right group.
Provisioning a whole class one device at a time is easy to lose track of. A session fixes this by giving the work a container. You open a session for a group, for example Class 7B, and every device you provision in it goes into that group with that group's policy and app list.
Inside a session you see the students of the group and their state: waiting, in progress, provisioned or failed. The dashboard generates the one-time token for the next student when you start, so you do not have to create them in advance. If a device fails, the student stays in the waiting state and you try again with a fresh token.
Sessions pair with the readiness gate. Before a session can start, the group must have a policy and an app list, and the device model must have a profile. This is why you will not discover on device twenty that the group has nothing to enforce. If provisioning has been frozen for the organisation, a session cannot create new devices until it is lifted.
A session is useful on the supervisory side too. A branch head can see that a class is half done, a teacher can see which students are still waiting for tablets, and a school can tell when a rollout is complete.
Practical tip: run one session per class and finish it before opening another. That keeps the dashboard list aligned with the physical trolley. See the readiness gate and how a laptop run works.
- One session per group
- Shows which students are done or waiting
- Needs a policy, an app list and a model profile
- Respects the provisioning freeze