What happens if I delete a catalog app that organisations are using?
Skie blocks the deletion. A catalog app that one or more organisations use cannot be deleted unless the removal is forced, which protects devices from losing an app mid-term by accident. Forcing it removes the app from those organisations' lists, so use the where-used view and tell the affected admins first.
The catalog is shared. When an organisation adds a catalog app to its store and lists, devices come to depend on it. If the app were simply deleted, students could lose a learning tool in the middle of a lesson, and several organisations could be affected at once.
So the default is protection. If you try to delete a catalog app that is in use, Skie stops you. The block tells you the app is in use, and you can look at where. A forced deletion is available for real cases, for example an app that has turned unsafe after an update, but it is a deliberate step, not an accident.
Apps are hidden or suspended on devices rather than deleted, so data is not wiped when an app leaves a list, and it returns if the app is allowed again. Even so, removing an app people rely on has a human cost, so communicate before you do it.
For your own organisation, the gentler route is almost always to take the app off the relevant app lists, or to leave it as a draft in your store, rather than touching the shared catalog. A practical tip: run the where-used check, warn the teachers who use the app, remove it from lists at a quiet time, and only then consider whether it should leave the store at all.