Extension does not install
Check chrome://policy for errors. Confirm the extension ID and update URL match this guide.
Chrome enterprise
Filterly installs by Chrome policy. Each managed Chromebook enrolls itself with a deployment token and appears in the console without per-device setup.
The extension ID is fixed at
fgcfcconedppccdaihnbplgabehjcnkp.
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 DeploymentIn 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:
{
"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.
chrome://policy and reload policy.chrome://extensions and confirm Filterly is installed and cannot be removed.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.
Check chrome://policy for errors. Confirm the extension ID and update URL match this guide.
Confirm the deployment token is correct and has not expired. Check the token under Deployment in the console.
The Chromebook cannot reach the WebSocket. Check DNS, firewall rules and whether filterly.pro is blocked.
Reload policy in Google Admin, then reopen chrome://policy on the device. It can take a few minutes.