How does the app list library work and can I reuse lists?
The app list library holds the lists your organisation has built, ready to attach to any group. You can reuse one list on many groups, fork it to make a variation, and see where each list is used. Reuse keeps classes consistent and changes quick, because you edit one list instead of many.
Like policies, app lists live in a shared library. You create a list once, such as 'Class 6 to 8 learning apps', and attach it to every group that should have it. When you add a new approved app to that list, every group using it gains the app on the next sync.
Forking works the same way as for policies. If one branch needs the same list plus a coding app, fork the list, add the app, and attach the copy to that branch only. The original stays unchanged for everyone else, and each copy has an owner who decides who may edit it.
Two checks keep reuse safe. The where-used view lists the groups attached to a list, so you know who a change will touch. The impact preview shows how many devices that is before you save. Together they stop a casual edit from reaching more classes than you meant.
Apps in the list come from your organisation app store, which is itself drawn from the Skie app catalog. That means a list can only hold apps that are available to your organisation. A practical tip: keep a small number of well-named lists and fork rarely. Dozens of near-duplicate lists are hard to audit, whereas a few clear ones, paired with schedules, cover most school and company needs.