SkieWhat is the curated list of web filters and who controls it?
The Skie owner curates a list of filtering DNS options, and organisation admins pick from that list for their organisation or groups. Admins cannot enter an arbitrary DNS address. This keeps every filter on a managed device a vetted one and still gives schools a real choice.
A free-text DNS field sounds flexible, but it creates risk. A mistyped address could leave a group unfiltered, and a malicious one could point the device at a resolver that logs or redirects. Skie keeps that decision out of the hands of day-to-day admins.
The owner role adds filters to the list after review. Each entry is a filtering DNS service with known behaviour. Organisation admins then choose one for the organisation, school, branch or group. Where nobody has chosen, the default filter applies, which is CleanBrowsing Family with a fallback host.
If a school has a requirement the list does not meet, for example a specific provider named in a regional education policy, the practical route is to ask the Skie team. They can consider adding it to the list for everyone who needs it. The list is the same for every organisation, so a request benefits others too.
The choice is stored as part of the policy, and the signed policy bundle carries it to the device. The device rejects anything that does not verify, so a forged DNS choice sent by a third party would not be applied.
Practical tip: record in your own policy document why you picked a given filter. When a parent or governor asks what is blocked, you can point to the provider's published categories and the Skie settings together.