Teams deployment guide

One org key licenses every seat. Pick the section that matches how you manage Chrome — or use the manual way at the bottom.

You'll need your organization key (from the checkout page or your receipt email) and the extension ID:

oaiklekamhihggihhoibgpbnfejlcppf

1. Google Workspace

Open the Admin console → Devices → Chrome → Apps & extensions.
Select the organizational unit that should get the extension.
Add the extension by ID (oaiklekamhihggihhoibgpbnfejlcppf) and set the installation policy to Force install.
Paste this into Policy for extensions, with your key in place of YOUR-ORG-KEY:
```
{ "orgLicense": { "Value": "YOUR-ORG-KEY" } }
```
Save.

To verify: the extension popup shows "Licensed by your organization ✓", and chrome://policy lists orgLicense under the extension.

2. Windows — GPO, Intune, or any MDM

Anything that can write a registry value works. Set one string value:

Key:    HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\oaiklekamhihggihhoibgpbnfejlcppf\policy
Value:  orgLicense  (REG_SZ)
Data:   YOUR-ORG-KEY

To force-install the extension too, add this entry to Chrome's standard ExtensionInstallForcelist policy:

oaiklekamhihggihhoibgpbnfejlcppf;https://clients2.google.com/service/update2/crx

3. macOS — any MDM with configuration profiles

Ship the same policy as a managed preferences plist for the preference domain com.google.Chrome.extensions.oaiklekamhihggihhoibgpbnfejlcppf:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>orgLicense</key>
  <string>YOUR-ORG-KEY</string>
</dict>
</plist>

4. No management tooling? The manual way

Each person:

Installs the extension from the Chrome Web Store.
Opens the extension popup → "Have a license key?"
Pastes the same org key → done.

Seats are counted automatically — there's no per-user setup beyond the paste.

5. Company styles (optional)

Push standardized styles — a brand header, a disclaimer gray — to every seat. Build each style once in Gmail (save it in the extension, then ⧉ copy as JSON from the popup's Saved styles list), paste the JSON below, and it's packaged for your deployment method. Styles appear read-only under "Company" on every managed seat and update whenever the policy does.

Exported style JSON (one style or a list, e.g. [{"name":"Brand header","style":{…}}]):

Workspace — add inside "Policy for extensions"

Windows registry — second string value, same key as above

macOS plist — second entry in the same dict

No management tooling? Keep the exported JSON in your wiki — everyone pastes it once via the popup's Import styles.

Troubleshooting

Policy can take a few hours to reach browsers — on a test machine, open chrome://policy and click Reload policies.
orgLicense should appear under the extension ID at chrome://policy with status OK.
Still stuck? [email protected] — a screenshot of chrome://policy gets the fastest answer.