SkieCan different schools or groups use different web filters?
Yes. An organisation can choose its own filter, and a school, branch or group below it can override that choice, so primary students and senior students can sit behind different levels of filtering. The most specific level applies last, and anything unset falls back to the default.
Skie policies flow down a hierarchy: organisation, school, branch, group, student and device. The web filter follows the same pattern. Set one at the organisation level and every device inherits it. Set another on a group and that group uses its own.
The filter you can pick comes from a list the Skie owner curates. Organisation admins choose from that list and cannot add arbitrary DNS addresses. This keeps the filter on the device to a vetted set of providers with known behaviour.
A typical set-up for a chain of schools: one strict filter at the organisation level for everyone, a slightly lighter filter for a senior-school group, and the browser switched off entirely for a primary group. Each decision is a policy choice, so nothing is hard-coded.
The effective policy view shows the filter in force for a group, and the impact preview tells you how many devices will change before you apply an edit. The where-used view shows which groups depend on a given policy, which helps before you modify a shared one.
Roles matter. A class admin or teacher does not usually pick the school's filter, and page access can be switched per role. If a teacher needs an exception for a lesson, use the app list or a lesson window instead of changing the filter, and ask the right admin for a filter change when it is needed for longer.