SkieWhat is a policy in Skie device management?
A policy in Skie is a named set of rules for a device: which protections are switched on, how the browser behaves, which hardware switches such as camera or Bluetooth are off, and which filter applies. It does not say which apps are allowed. That lives in a separate app list. You attach a policy to a group, and every device in it follows the policy.
Think of a policy as the rulebook for the hardware and the settings. It holds the hardening switches (factory reset blocked, safe mode blocked, developer options blocked and so on), the Chrome rules, the web filter choice, and the optional switches like camera, SMS, outgoing calls, Bluetooth, screenshots and USB. Most of the hardening switches are on by default. The optional ones are off until you choose them.
Apps are kept apart on purpose. A policy answers how the device behaves. An app list answers what is on it. Because they are separate, you can keep one strict policy and swap app lists for Class 6 and Class 10, or keep one app list and apply a tighter policy to a hostel block. Each group has one policy and one app list at a time.
Policies are signed before they reach a device, and the device rejects anything that does not verify. After every apply the device reads each protection back from Android and reports a compliance score, so you can see that the rule actually took effect rather than assuming it did. Rules are cached on the device and keep working when the network drops.
A practical tip: start from a template in the policy library rather than a blank page, then change only what your institution needs. Use the impact preview before you save, so you know how many devices will change.