Force-install Capsulla from Google Admin.
Ten minutes in a console you already use, and nobody on staff has to do anything. These are the same steps the Capsulla console walks you through after you sign up, written out here so you can read them before you commit to anything.
Before you start
- A super admin account in Google Admin, or a custom role with the Chrome Management privilege.
- Chrome browsers enrolled in your Google Admin. Policy only reaches browsers that are enrolled.
- Your organization key from the Capsulla console. It looks like cap_ followed by hex characters, and the console shows it with a copy button.
- 01
Open the right page in Google Admin
Sign in at admin.google.com and go to Devices ▸ Chrome ▸ Apps & extensions ▸ Users & browsers. On the left, pick the organizational unit or group you are rolling out to.
Start with one OU rather than the whole company. A pilot group tells you what your rules catch before anybody else notices they exist.
- 02
Add the extension
Click the yellow + button and choose Add from Chrome Web Store. Search for Capsulla and select it. If you would rather be exact, use Add Chrome app or extension by ID from the same menu and paste the extension ID below, leaving the source as the Chrome Web Store.
Extension IDmlkicompblcckemkmmphgnebgfapdpbf - 03
Set the installation policy to Force install
Click the new Capsulla row. Under Installation policy, choose Force install — or Force install + pin to ChromeOS taskbar if you run ChromeOS. Save.
Force install is what makes this an administrative control rather than a request: the person using the browser cannot remove or disable the extension.
- 04
Push your organization key
Still on the Capsulla row, find Policy for extensions and paste one line of JSON with your key in it. That is the entire configuration that ships to a browser — rules, retention and alerts are all decided in the console afterwards.
Paste into “Policy for extensions”{ "orgKey": "cap_org-code" } - 05
Check that it arrived
Changes can take up to 24 hours to reach every device, though most browsers pick them up within minutes of a restart. On a test machine, open chrome://policy and click Reload policies to force it immediately. In the Capsulla console, the setup step marks itself done when the first browser reports in, and the browsers page fills up from there.
When something does not land
A browser does not appear in the console
Three usual causes: the browser is not enrolled in your Google Admin, it sits in a different organizational unit from the one you configured, or it has not picked up the policy yet. chrome://policy on that machine shows what it actually received.
The extension is installed but the console stays empty
That is almost always the key. Check that Policy for extensions carries the orgKey line exactly, with your own key rather than the example, and that it is set on the same organizational unit as the force-install.
You need to stop it on one group
Change the installation policy for that organizational unit back to Allow install or Block. The extension disappears on the next policy refresh, and the events it already recorded stay in the console until the retention window ends.
What happens next
Nothing has to block on the first day. Leave the shipped rules on warn, let a week pass, and read what the log filled up with — then decide which of it is worth stopping.
For Google WorkspaceGoogle changes the labels in Admin occasionally. If a name here does not match what you see, the path is the same: Chrome, then apps and extensions, then your organizational unit.
Stop the next leak before it leaves the browser.
Try it free for 14 days, no card needed. Start with one team and see what Capsulla catches in the first week.