Which Chrome rules does Skie enforce on managed devices?

These rules apply to Chrome stable, beta, dev and canary. Because Skie runs as the Android device owner, Android itself enforces them. The student does not see a setting to change and cannot install a different channel to escape them.

The rules fall into three groups. Content: SafeSearch, YouTube Restricted Mode, the safe-sites filter and safe browsing. Routing: Chrome's own secure DNS off so the filtered system DNS is used, and the search engine locked to Google. Closing side doors: incognito blocked, sign-in blocked, sync disabled, pop-ups and notifications blocked, and chrome://flags, net-internals, inspect, view-source and javascript: pages blocked.

Chrome itself can be off, restricted or allowed per group. Where it is allowed, these rules come with it. Where it is off, the rules have nothing to enforce, and the browser does not appear.

Each rule has its own entry in this knowledge base with the reasoning. Start with the ones that your staff ask about most, which in practice are SafeSearch, incognito and the flags page.

After every apply, the device reads each protection back from Android and reports a compliance score. If a Chrome rule is not in force, it shows against that device and the breach centre can alert the right admin. Practical tip: check one pilot device's effective policy before explaining the set to staff, so your briefing matches what the dashboard shows.