How does app approval work in Skie?

Skie for Enterprise · Updated

Short answer

When an organisation adds an app that is not in the Skie catalog, the entry goes to the Skie team for review. It shows as waiting for Skie until approved. Approved apps can be published to the organisation store and added to lists. Approval is on by default and the owner can turn it off for a trusted organisation.

The flow has four steps. An admin adds an app by pasting its Google Play link. The entry is saved, and because it is new to Skie it is marked as waiting for Skie. The team reviews it. Once approved, the admin can publish it and put it on an app list.

The review is there to keep the shared platform safe. Skie curates the catalog, and an app that turns bad after an update can be removed. The same care applies to apps that organisations add, since the device will run them for students and staff.

Approval is about availability, not about attachment. An approved app is not on any device until an admin puts it on a list and attaches that list to a group. So even approved apps go through your own choice of who gets them.

Admins sometimes ask how long approval takes. The status simply shows waiting for Skie until it is done, and there is no promised timing in the product, so plan ahead for term starts. If your organisation is trusted and adds apps often, ask the Skie owner about turning approval off. A practical tip is to keep a short request note with each app, saying which class needs it and why, so reviewers and your own colleagues can see the reason later.