Filterly

Chrome enterprise

Set up Filterly

Filterly installs by Chrome policy. Each managed Chromebook enrolls itself with a deployment token and appears in the console without per-device setup.

Requirements

  • A Google Admin super admin account.
  • Chromebooks managed by your school or district.
  • Access to the Filterly console at filterly.pro/manage.
  • The student OU or browser OU you want to target.

The extension ID is fixed at fgcfcconedppccdaihnbplgabehjcnkp.

1 Create a deployment token

Sign in to the console, open Deployment, then choose New token. Use a name for the rollout, set an expiry and copy the token when it appears. The token is shown only once.

Open Deployment

2 Add the policy

In Google Admin, open Devices, Chrome, Settings, then Users & browsers. Select the student OU and open the raw policy editor.

Paste this policy and replace the placeholder token:

chrome-policy.json
{
  "ExtensionSettings": {
    "fgcfcconedppccdaihnbplgabehjcnkp": {
      "installation_mode": "force_installed",
      "update_url": "https://filterly.pro/ext/update.xml",
      "toolbar_pin": "force_pinned",
      "blocked_install_message": "Filterly is required on this device. Contact your administrator."
    }
  },
  "IncognitoModeAvailability": 1,
  "3rdparty": {
    "extensions": {
      "fgcfcconedppccdaihnbplgabehjcnkp": {
        "deploymenttoken": "flt_replace_with_your_token"
      }
    }
  }
}

The policy example is also available at /setup/chrome-policy.json.

3 Apply by organizational unit

  1. Start with a pilot OU, not the whole district.
  2. Paste the policy and save the change.
  3. On a test Chromebook, open chrome://policy and reload policy.
  4. Confirm the extension policy shows no errors.

4 Verify the device

  1. Open chrome://extensions and confirm Filterly is installed and cannot be removed.
  2. Open the console and check that the device appears under Devices.
  3. Confirm the device shows online and starts reporting activity.
  4. Open a test page and confirm the popup shows Filterly is active.

5 Roll out

After the pilot works, apply the same policy to the remaining student OUs. New devices enroll as policy arrives. Existing devices enroll after the extension updates or the browser restarts.

Changes to detection mode, exclusions, alerts and device access are managed from the Filterly console. You do not need to edit policy for those changes.

Troubleshooting

Extension does not install

Check chrome://policy for errors. Confirm the extension ID and update URL match this guide.

Device does not appear

Confirm the deployment token is correct and has not expired. Check the token under Deployment in the console.

Waiting for Filterly to start

The Chromebook cannot reach the WebSocket. Check DNS, firewall rules and whether filterly.pro is blocked.

Policy change did not apply

Reload policy in Google Admin, then reopen chrome://policy on the device. It can take a few minutes.