Home Device Management Enrolling Chromebooks via Google Admin

Enrolling Chromebooks via Google Admin

Last updated on Apr 17, 2026

Enrolling Chromebooks via Google Admin

KyberGate protects Chromebooks through a Chrome browser extension that's force-installed via Google Admin Console. This guide covers the complete setup process for deploying KyberGate across your Chromebook fleet.

Before You Begin

  • Google Admin Console access with super admin or Chrome management privileges
  • Google Workspace for Education account (the Chromebooks must be managed)
  • KyberGate admin access to retrieve your extension ID and org credentials
  • Chromebooks must be running ChromeOS 100 or later
  • Estimated setup time: 10–15 minutes

Step 1: Get Your KyberGate Extension ID

  1. Log in to dashboard.kybergate.com
  2. Navigate to Devices → Enrollment → Chromebook
  3. Copy the Chrome Extension ID (a 32-character alphanumeric string)
  4. Also note your Organization ID — the extension uses this to identify your school

Step 2: Force-Install the Extension in Google Admin

  1. Log in to admin.google.com

  2. Navigate to Devices → Chrome → Apps & Extensions → Users & Browsers

  3. Select the Organizational Unit (OU) where you want to deploy KyberGate

    • For district-wide deployment, select the top-level OU
    • For grade-level deployment, select the appropriate sub-OU

  4. Click the + (Add) button at the bottom right

  5. Select Add Chrome app or extension by ID

  6. Paste the KyberGate Extension ID

  7. Choose From the Chrome Web Store

  8. Click Save

  9. The extension entry will appear in the list. Click on it to configure:

    • Installation policy: Set to Force install (this ensures students cannot remove it)
    • Update URL: Leave as default (Chrome Web Store)
    • Allow incognito mode: Set to Force (ensures filtering works in incognito)

  10. Click Save at the top right

💡 Pro Tip: The "Force install" setting is critical. If set to "Allow install," students can remove the extension and bypass filtering entirely.

Step 3: Configure Extension Policy (Optional)

You can pass configuration parameters to the extension via Google Admin:

  1. In the extension settings, find Policy for extensions
  2. Enter the JSON configuration: 
    {
  "orgId": "YOUR_ORG_ID",
  "proxyMode": "auto",
  "reportingLevel": "full"
}
  3. Click Save

Step 4: Block Extension Removal and Developer Mode

To prevent students from bypassing KyberGate:

  1. In Google Admin, go to Devices → Chrome → Settings → Users & Browsers
  2. Select your target OU
  3. Configure:
    • Developer tools: Set to Never allow use of built-in developer tools
    • Incognito mode: Set to Disallow incognito mode OR ensure the extension is forced in incognito
    • Chrome Web Store permissions: Restrict to approved extensions only

Step 5: Verify Enrollment

  1. Have a student sign in to a Chromebook in the targeted OU

  2. Open Chrome and click the puzzle piece icon (Extensions) in the toolbar

  3. The KyberGate extension should appear with "Installed by your administrator"

  4. Browse to a site in a blocked category — the KyberGate block page should appear

  5. In the KyberGate dashboard:

    • Navigate to Devices
    • The Chromebook should appear with:
      • Device name
      • Student email (from Google account)
      • Status: 🟢 Online
      • Last check-in time

Step 6: Roll Out to All Chromebooks

Once testing is successful:

  1. Return to Google Admin → Devices → Chrome → Apps & Extensions
  2. Either:
    • Apply the extension to higher-level OUs to cover more students
    • Or move students/devices into the OU where KyberGate is deployed
  3. Extensions propagate to devices on next Chrome restart or within ~15 minutes

Advanced Configuration

Different Policies for Different OUs

You can configure different KyberGate organizations or policies for different OUs:

  • Create separate KyberGate "groups" in the dashboard
  • Pass different orgId values in the extension policy for different OUs

Managed Guest Sessions / Kiosk Mode

KyberGate works in managed guest sessions and kiosk mode. Ensure the extension is force-installed for the managed guest session OU.

Handling Shared Chromebooks

On shared Chromebooks, KyberGate identifies users by their Google account. Different students on the same device are tracked and filtered individually.

Troubleshooting

Extension not appearing on Chromebooks:

  • Verify the OU assignment — the student's account must be in the OU where the extension is deployed
  • Force a Chrome policy refresh: Open chrome://policy and click Reload policies
  • Restart Chrome completely (close all windows)
  • Check the extension ID is correct — a single typo will prevent installation

Students see "Not installed by your administrator":

  • The installation policy is set to "Allow install" instead of "Force install"
  • Update the policy in Google Admin to "Force install"

Filtering not working despite extension being installed:

  • Open the extension popup — it should show "Connected" and your school name
  • If it shows "Disconnected," check network connectivity
  • Verify the orgId in the extension policy matches your KyberGate organization

Extension crashes or becomes unresponsive:

  • Update ChromeOS to the latest version
  • Go to chrome://extensions, find KyberGate, and check for error logs
  • Contact KyberGate support with the error details

Related Articles