SkieCan I see who a policy change will affect before I save it?
Yes. Before a change to a policy or app list is applied, Skie shows an impact preview listing the groups and devices it will touch. You review it, then confirm or cancel. Nothing changes until you confirm. It is the main safeguard against editing a shared policy and affecting more devices than you meant.
In Skie, one policy and one app list can sit over many groups, and rules flow down the structure. That is powerful, and it means a small edit can have a wide reach. The impact preview is there to stop surprises.
When you make a change, the preview shows which groups and devices will be affected. If you edit the policy used by an entire school, you see the whole school. If you edit one used by a single class, you see the class. You can then decide whether this is what you meant or whether to create a fork for just one group instead.
Other views help. The where-used view shows what depends on a policy or app list. The effective policy view shows what a single device ends up with after all levels are combined, remembering that blocking beats allowing. Together they explain not only what will change but why a device behaves as it does.
After you confirm, the signed policy goes to devices. Online ones take it within seconds, and others at their next sync, and you can watch on latest policy climb. The change is recorded in the audit log, and if it was a mistake, the restore options let you go back.
Practical tip: use the preview as a trigger to tell people. If it shows 300 devices in a school, a note to teachers before you confirm will save you a day of questions. For a first-time rollout, test on a small group first; see run a pilot.