SkieHow are blocked websites and the web filter set in a policy?
The policy chooses the web filter, and the filter blocks categories of sites such as adult content. The filtering DNS is locked on the device, so it applies on any Wi-Fi or mobile data. Chrome rules like SafeSearch are enforced too. Custom per-website block lists are not available yet.
Web safety comes from two layers in a Skie policy. The first is Chrome: SafeSearch forced, YouTube restricted mode forced, the safe-sites filter on, safe browsing on, incognito blocked, sign-in and sync blocked, pop-ups and notifications blocked, and Chrome's own secure DNS off so the filtered system DNS is used.
The second is the filtering DNS. Unless your organisation or group has chosen another, the default is CleanBrowsing Family, with a fallback host. The owner curates a list of filters and organisation admins choose from it. A group-level choice overrides the organisation's. The setting is locked on the device, and a bypass is reported.
A blocked site simply fails to load. Because it is DNS-based, the filter sees domain lookups, not page content. Some networks block the encrypted DNS port; then the device uses the network's own DNS and the dashboard flags it. A network check wizard tests your school Wi-Fi in advance.
Browsers can be off, restricted or allowed per group, and more than fifty alternative browsers are always blocked. Per-website allow or block lists are not available yet, and the team is working on them, with no dates. Until then, choose the filter closest to your need and use the app list to control what runs. A practical tip: run the network check before term starts, and read safe browsing for students.