School web filtering · In development · Pilot release

Clear boundaries.
Room to learn.

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.

One organization policy. Beyond the bell.Managed Chromebooks · Local filtering · Cached offline policy

In development · Product direction

The right access.
A clearer way to manage it.

Keep your school’s web filtering in its own workspace, with controls for the administrators responsible for it.

01 / Define

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
02 / Enforce

Keep decisions local.

A managed Chrome extension applies rules on the Chromebook. Cached policy continues between syncs, including when the policy service is unreachable.

  • Local browser enforcement
  • Cached offline policy
  • No student settings panel
03 / Oversee

Know what’s connected.

Manage your organization’s enrollment and review device coverage and last-seen information from the administrator console.

  • Organization enrollment
  • Device coverage visibility
  • Administrator-only access

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.

Set the policy.
Let the device carry it.

The console manages policy. The Chromebook makes the filtering decision locally, without sending browsing traffic through a CampusOps cloud proxy.

Built for managed ChromeOS
  1. 1

    Configure your organization

    An administrator selects the filtering mode and sets the school’s rules.

  2. 2

    Enroll managed Chromebooks

    Deploy the separate Web Policy extension through Google Admin with your organization’s enrollment settings.

  3. 3

    Sync, enforce, and review

    Devices retrieve policy and enforce it locally. Administrators review coverage and update rules as needs change.

A focused product. A familiar family.

A few useful answers.

How is this different from ClassOrbit?

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.

Does the policy depend on a teacher starting a session?

No. Organization policy is designed to remain in effect on enrolled, managed Chromebooks outside classroom sessions, including after the school day.

What happens if the policy service cannot be reached?

The extension continues applying its cached policy locally. New policy changes require the device to reconnect and synchronize.

Can students change the filtering settings?

The managed extension has no student configuration screen. Policy is controlled by organization administrators; school-managed enrollment and extension deployment are required.

Can our school start using it today?

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

Start with your
school’s needs.

Tell us about your Chromebook fleet, current filtering setup, and the controls you need. Share your requirements with our team as development continues.

Email the Web Policy team ↗sales@campusopshq.comOpens a draft in your email app. Send it to register your interest.