Format Painter for Gmail

Teams deployment guide

One team license key covers every seat. Two things reach each browser: the extension, and your key, delivered as Chrome extension policy. Pick your path.

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

oaiklekamhihggihhoibgpbnfejlcppf

Google Workspace

Admin console pushes the install and the key
  1. Admin console → Devices → Chrome → Apps & extensions → Users & browsers tab.
  2. Select the organizational unit or group that should get it.
  3. Click + → Add Chrome app or extension by ID → enter the extension ID → Save.
  4. Click the new entry and set Installation policy to Force install.
  5. Paste into Policy for extensions, with your key in place of YOUR-TEAM-KEY, and Save: 
    { "orgLicense": { "Value": "YOUR-TEAM-KEY" } }

Verify on a test machine: chrome://policy → Reload policies. orgLicense appears under the extension and the popup reads "Licensed by your team." Workspace policy can take up to 24 hours to reach everyone.

More detail: Google's guide to automatically installing extensions.

Windows

Intune, Group Policy, or any tool that writes registry

Two registry values do everything. Deliver them however you already manage Windows; Chrome applies them on its next policy refresh, no restart and no domain join required.

Force-install:
HKLM\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist
  "1" (REG_SZ) = oaiklekamhihggihhoibgpbnfejlcppf

License key:
HKLM\SOFTWARE\Policies\Google\Chrome\3rdparty\extensions\oaiklekamhihggihhoibgpbnfejlcppf\policy
  orgLicense (REG_SZ) = YOUR-TEAM-KEY

The extension ID on its own is a complete force-install entry; Chrome installs and updates from the Web Store automatically. Older guides append ;https://clients2.google.com/service/update2/crx, which also works.

Step-by-step walkthroughs for the two common systems are below. On any other MDM or RMM, deliver the two values directly (write the registry keys, or run Set-FormatPainterLicense.ps1 as SYSTEM); the Intune and Group Policy steps translate one-to-one.

Intune steps
  1. Force-install the extension. Devices → Manage devices → Configuration → Create → New policy → Windows 10 and later → Settings catalog. Search "force-installed" and pick the setting from the Google Google Chrome Extensions category, Configure the list of force-installed apps and extensions. (Not Configure list of force-installed web apps under Google Google Chrome; that one is for websites, not extensions.) Set it Enabled with one entry, the extension ID by itself: 
    oaiklekamhihggihhoibgpbnfejlcppf
  2. Add the license key. Pick one of three:
    • ADMX template (recommended) The key becomes a labeled policy field; no script to edit. Devices → Manage devices → Configuration → Import ADMX tab → Import → upload FormatPainterForGmail.admx + en-US .adml. The template is self-contained (no need to import Google's Chrome ADMX first) and carries only the license and company-styles settings; force-install stays in step 1. Then create the profile: New policy → Windows 10 and later → Templates → Imported Administrative templates → Format Painter for Gmail → Team license key → Enabled → paste your key.
    • Remediation Re-applies the key on a schedule and reports per-device compliance; needs Remediations licensing (Windows E3/E5 or A3/A5). Devices → Scripts and remediations → Remediations → Create. Detection script: Detect-FormatPainterLicense.ps1. Remediation script: Set-FormatPainterLicense.ps1. Edit the same key into both. Run using logged-on credentials: No; 64-bit host: Yes; schedule daily.
    • Platform script Simplest, runs once per device. Devices → Scripts and remediations → Platform scripts → Add → upload Set-FormatPainterLicense.ps1 with your key edited in. Run using logged-on credentials: No; 64-bit host: Yes. Edit and re-save the script to push a changed key later.
  3. Assign the profiles and script to your device group.
Group Policy steps
  1. Force-install: with Google's Chrome ADMX templates in your Central Store (most Chrome shops already have them): Computer Configuration → Administrative Templates → Google → Google Chrome → Extensions → Configure the list of force-installed apps and extensions → Enabled → one entry, the extension ID oaiklekamhihggihhoibgpbnfejlcppf.
  2. License key: drop FormatPainterForGmail.admx into PolicyDefinitions and the .adml into its en-US subfolder, then: Computer Configuration → Administrative Templates → Format Painter for Gmail → Team license key → Enabled → paste your key. Prefer raw registry? A Group Policy Preferences registry item with the values above does the same job.

Downloads

  • FormatPainterForGmail.admx + en-US\FormatPainterForGmail.adml: our policy template, for Intune's ADMX import or a GPO PolicyDefinitions folder. It adds two settings under Format Painter for Gmail, Team license key and Company styles. It does not force-install the extension; that is Chrome's own policy, set in step 1 of either walkthrough.
  • Set-FormatPainterLicense.ps1: writes the license (and optional company styles) registry values as SYSTEM. Works as an Intune platform script, as the remediation half of the Remediations pair, or from any RMM that runs PowerShell.
  • Detect-FormatPainterLicense.ps1: the matching detection script for Intune Remediations. Exits compliant when the key is already present and correct.
  • format-painter-license.reg: the license value only. Double-click it on a test PC to check your key before rolling out fleet-wide.

Verify on a test PC: chrome://policy → Reload policies. Both values show status OK and the popup reads "Licensed by your team."

More detail: how Chrome reads extension policy.

macOS

Jamf or any MDM with configuration profiles

Fastest path: download FormatPainter-macOS.mobileconfig, put your key in place of YOUR-TEAM-KEY, and upload it as a custom configuration profile in any MDM. One profile force-installs the extension and applies the license. Already force-installing another way? Delete its com.google.Chrome payload and keep the license payload.

Building your own profile instead? Two managed preference domains:

License:
com.google.Chrome.extensions.oaiklekamhihggihhoibgpbnfejlcppf
  orgLicense (string) = YOUR-TEAM-KEY

Force-install:
com.google.Chrome
  ExtensionInstallForcelist (array) + "oaiklekamhihggihhoibgpbnfejlcppf;https://clients2.google.com/service/update2/crx"
Jamf Pro steps
  1. Computers → Configuration Profiles → New. Name it; Level: Computer Level.
  2. Application & Custom Settings → Upload → Add. Preference Domain: com.google.Chrome.extensions.oaiklekamhihggihhoibgpbnfejlcppf
  3. Paste this property list with your key swapped in, or upload it as a file (ready-made plist): 
    <?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-TEAM-KEY</string>
</dict>
</plist>
  4. Scope to your Macs and Save.

Prefer a labeled form field? Use the External Applications tab with our custom schema.

Verify on a Mac: the profile appears in sudo profiles show, chrome://policy lists orgLicense, and the popup reads "Licensed by your team."

More detail: how Chrome reads extension policy.

No management tooling

Each person pastes the key once
  1. Install from the Chrome Web Store.
  2. Open the extension popup → "Have a license key?"
  3. Paste the same team license key. Done; seats count automatically.

Ignore "seats" and "invite member" in the billing portal; those are our payment processor's generic tools. Licensing is only this key.

Company styles

Optional: push standardized styles to every seat

Save a style in the extension, use ⧉ copy as JSON in the popup's Saved styles list, and paste it below. The button reshapes it for each platform, entirely in your browser; nothing is uploaded. Deploy the result as a second value, orgPresets, right beside orgLicense. Styles appear read-only under "Company" on every managed seat and update whenever the policy does.

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

Troubleshooting

  • Policy lands in minutes via MDM sync, up to 24 hours on Google Workspace. On a test machine, chrome://policy → Reload policies applies it immediately.
  • 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.