Set the boundaries.
Choose baseline, aggressive, or allowlist mode to fit your school’s needs. Refine the policy with category, domain, and URL-term controls.
- Three enforcement modes
- Custom allow and block rules
- School-branded block messages
School web filtering · In development · Pilot release
Campus Web Policy gives your school a consistent web policy beyond the classroom session, with administrator-managed Chromebook filtering and local device enforcement.
A standalone CampusOps HQ product for school IT teams.
In development · Product direction
Keep your school’s web filtering in its own workspace, with controls for the administrators responsible for it.
Choose baseline, aggressive, or allowlist mode to fit your school’s needs. Refine the policy with category, domain, and URL-term controls.
A managed Chrome extension applies rules on the Chromebook. Cached policy continues between syncs, including when the policy service is unreachable.
Manage your organization’s enrollment and review device coverage and last-seen information from the administrator console.
These are planned product capabilities under active development and are available through the pilot release. Features and supported environments may change as the product develops.
Cloud managed. Device enforced.
The console manages policy. The Chromebook makes the filtering decision locally, without sending browsing traffic through a CampusOps cloud proxy.
Built for managed ChromeOSAn administrator selects the filtering mode and sets the school’s rules.
Deploy the separate Web Policy extension through Google Admin with your organization’s enrollment settings.
Devices retrieve policy and enforce it locally. Administrators review coverage and update rules as needs change.
A focused product. A familiar family.
Campus Web Policy focuses on ongoing, organization-wide web filtering managed by administrators. ClassOrbit focuses on classroom sessions, teacher-led workflows, and device visibility. Web Policy has its own console and extension, independent of classroom sessions.
No. Organization policy is designed to remain in effect on enrolled, managed Chromebooks outside classroom sessions, including after the school day.
The extension continues applying its cached policy locally. New policy changes require the device to reconnect and synchronize.
The managed extension has no student configuration screen. Policy is controlled by organization administrators; school-managed enrollment and extension deployment are required.
Yes. Start an organization to create an isolated administrator workspace, then deploy the managed extension to a test Chromebook before wider rollout. Existing administrators can sign in here.
Let’s talk web policy
Tell us about your Chromebook fleet, current filtering setup, and the controls you need. Share your requirements with our team as development continues.