Skip to main content

Mass Deploying the Spekit Chrome Extension

  • Updated

📌 Quick-Jump Topics

 

Overview

For organizations that want to deploy the Spekit Chrome extension across multiple devices without requiring manual installation by end users, there are several enterprise deployment methods available. This article provides an overview of the three most common approaches: Google Workspace Admin Console, Mobile Device Management (MDM), and Windows Group Policy.

Each method allows you to force-install the extension, meaning it will be automatically installed on managed devices and users will not be able to remove it.

 

Choosing a Deployment Method

The best deployment method depends on your existing infrastructure. Google Workspace Admin Console is the simplest option for organizations already managing Chrome through Google. MDM provides flexibility for mixed-device environments and integrates with your existing device management workflows. Group Policy is a natural fit for Windows-centric organizations with Active Directory.

Some organizations use a combination of these methods to cover different device populations. For example, you might use Google Workspace for Chromebooks, MDM for macOS devices, and Group Policy for Windows machines.

 

Google Workspace Admin Console

If your organization uses Google Workspace (formerly G Suite), you can deploy Chrome extensions through the Google Admin Console. This method is ideal for organizations that manage Chrome browsers or Chromebooks through Google Workspace and works for both managed Chrome browsers on any operating system.

Prerequisites: You will need administrator access to your Google Admin Console and the Spekit extension ID (nbphjjmibhopfgkkbpoggemjnihnchhk) from the Chrome Web Store.

Deployment steps:

1. Sign in to your Google Admin Console at admin.google.com.

2. Navigate to Devices > Chrome > Apps & extensions.

3. Select the Users & browsers tab to deploy to users on any device, or choose Managed guest sessions for ChromeOS guest sessions.

4. On the left, select the organizational unit (OU) you want to target. To deploy to all users, leave the top-level OU selected. Child OUs will inherit settings from their parent unless overridden.

5. Hover over the plus (+) icon in the bottom-right corner and select Add Chrome app or extension by ID.

6. Enter the Spekit extension ID and click Save.

7. Click on the newly added Spekit extension to open its settings panel.

8. Under Installation policy, select Force install (or Force install + pin to browser toolbar if you want the extension icon always visible).

9. Click Save. The extension will automatically install on targeted browsers during the next policy sync.

For complete documentation, see Google's guide: Automatically install apps and extensions

 

Windows Group Policy

For Windows environments managed through Active Directory, Group Policy provides a native method for deploying Chrome extensions. This approach requires importing Google Chrome's administrative templates (ADMX files) into your Group Policy environment.

Prerequisites: You will need the Spekit extension ID, domain administrator access, and the Chrome ADMX templates from Google.

Step 1: Install the Chrome ADMX templates

Download the Chrome Enterprise Bundle or standalone ADMX templates from Google's Chrome Enterprise download page.

  1. Navigate to Start > Run: gpedit.msc. (Or run gpedit.msc in your terminal)
  2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates.
  3. Right-click Administrative Templates, and select Add/Remove Templates.
  4. Add the chrome.adm template via the dialog.

Once complete, a Google / Google Chrome folder will appear under Administrative Templates if it's not already there. If you added the ADM template on Windows 7 or 10, it will appear under Classic Administrative Templates / Google / Google Chrome.

Step 2: Configure the force-install policy

Open the Group Policy Management Console and create or edit a GPO linked to the organizational unit containing your target computers or users.

Navigate to Computer Configuration > Policies > Administrative Templates > Google > Google Chrome > Extensions (or User Configuration for user-based deployment).

Open the setting Configure the list of force-installed apps and extensions and set it to Enabled.

Click Show to open the extension list, then add a new entry in the following format:

[extension-id];https://clients2.google.com/service/update2/crx

Replace [extension-id] with the Spekit extension ID (nbphjjmibhopfgkkbpoggemjnihnchhk). 

Click OK to save, then close the policy editor.

Step 3: Apply and verify

Run gpupdate /force on target machines or wait for the next Group Policy refresh cycle. You can verify the policy was applied by opening chrome://policy on a target machine and checking for the ExtensionInstallForcelist policy.

For complete documentation, see Google's guide: Set Chrome browser policies on managed PCs and Set Chrome app and extension policies (Windows). 

Note: If you are using Edge at your organization, you can install the Spekit Chrome extension since Edge is based on Chromium. The same general concepts and steps mentioned above apply when you are deploying the extension to Edge. Please refer to the following Microsoft documentation if needed: Use group policies to manage Microsoft Edge extensions

 

Mobile Device Management (MDM)

Organizations using an MDM solution can typically deploy Chrome extensions as part of their device management policies. This method is particularly useful for organizations managing a mixed fleet of devices across macOS, Windows, and other platforms.

MDM solutions deploy Chrome extensions by pushing configuration profiles or policies to managed devices. These policies instruct the Chrome browser to install and pin specific extensions. The exact configuration steps vary depending on which MDM platform your organization uses.

Consult your MDM provider's documentation for specific instructions on deploying Chrome extensions. You will generally need the Spekit extension ID (nbphjjmibhopfgkkbpoggemjnihnchhk) and may need to configure the extension update URL (https://clients2.google.com/service/update2/crx) as well. 

Related articles