Deploy KyberGate Chrome Extension
to Your Chromebook Fleet
Force-install the KyberGate extension to all managed Chromebooks via Google Admin Console. Takes about 15 minutes. No student interaction required.
Before You Start
Google Admin Console access (admin.google.com) with Super Admin or Chrome Management privileges
A KyberGate organization — sign up at dashboard.kybergate.com if you haven't
Your KyberGate Organization ID (found in Dashboard → Settings → School Information)
KyberGate Chrome Extension
Extension ID: aodjgiobchlnlmicciieahkfnmkoojef
Chrome Web Store: Approved & Live
Open Google Admin Console
Go to admin.google.com and sign in with your admin account.
Navigate to: Devices → Chrome → Apps & extensions
Select the organizational unit (OU) you want to deploy to. You can choose the top-level org for all Chromebooks, or a specific OU like "Student Devices" for targeted deployment.
Add the KyberGate Extension
Click the + (Add) button in the bottom-right corner, then select "Add from Chrome Web Store".
Search for "KyberGate" or paste the Extension ID directly:
Click "Select" to add it to your extension list.
Set to Force Install
Click on the KyberGate extension in your list. In the right panel, change the installation policy:
Installation Policy
"Force install" means students cannot remove or disable the extension. It installs automatically on all Chromebooks in the selected OU.
Configure Extension Policy (Optional)
If you need to pre-configure the extension with your Organization ID, paste this JSON into the "Extension policy" field:
{
"orgId": {
"Value": "YOUR_ORG_ID_HERE"
}
}Replace YOUR_ORG_ID_HERE with your actual Organization ID from the KyberGate dashboard (Settings → School Information).
Note: If you skip this step, teachers and staff can enter the Org ID manually through the extension popup after installation.
Save & Deploy
Click "Save" in the top-right corner. The extension will begin deploying to all Chromebooks in the selected OU.
⏱ Deployment Timeline
Google Admin changes can take up to 24 hours to propagate to all devices. Most devices will receive the extension within 1–2 hours. Force a sync on any device by going to chrome://policy and clicking "Reload policies".
Verify Deployment
After deployment, verify on a test Chromebook:
- Open Chrome and look for the KyberGate shield icon in the toolbar
- Click the icon — it should show "Connected" with your school name
- Visit a blocked site (e.g., a known gaming site) — you should see the KyberGate block page
- Check the KyberGate dashboard — the device should appear in your Devices list within a few minutes
You can also verify installation status across your fleet in Google Admin Console under Devices → Chrome → Apps & extensions → Usage.
Recommended Google Admin Settings
For maximum protection, also configure these Chrome policies in your Google Admin Console:
Prevents unfiltered browsing
Prevents students from removing managed extensions
Prevents unmanaged browsing sessions
Prevents bypassing via Linux apps
Prevents VPN/proxy app installs
Prevents students from inspecting extension details
Using Alongside the Proxy (Recommended)
The Chrome extension provides web filtering for Chromebooks. For maximum protection, we recommend also deploying the KyberGate cloud proxy via PAC file — this catches traffic from Android apps, Linux containers, and other non-Chrome browsing.
Both can run simultaneously. The proxy handles network-level filtering while the extension provides enhanced classroom management features like screen view and tab locking.
View proxy setup guideTroubleshooting
Extension isn't appearing on Chromebooks
Wait up to 24 hours for propagation. Force a policy reload on the device: open chrome://policy and click 'Reload policies'. Ensure the device is in the correct OU.
Extension installs but shows 'Not Connected'
The extension needs your Organization ID. Either configure it via extension policy (Step 4) or have a teacher enter it through the extension popup.
Students can still access blocked sites
Verify the extension is force-installed (not just 'allowed'). Check that your KyberGate policies include the categories you want blocked. Allow 5 minutes for policy sync after changes.
Extension conflicts with another web filter
KyberGate can run alongside other extensions. If you see conflicts, ensure both aren't trying to redirect to different block pages for the same URL.
Need Help Deploying?
Our team can walk you through the deployment process and help configure policies for your district.