Deploying uBlock Origin - uBlockOrigin/uBlock-issues GitHub Wiki
I do not know much about enterprise deployment, so best to have knowledgeable people guide you:
- Improve performance and security by blocking ads on Windows Amazon WorkSpaces
- Managing Google Chrome with adblocking and security [via archive.org] by SwiftOnSecurity
- Deploy Firefox in the Enterprise with uBlock Origin, HTTPS Everywhere and Privacy Badger using Group Policy by John
- How To Deploy AdBlocker for Enterprise by Secjuice
- Tutorial: Deploying uBO configuration for Microsoft Edge Chromium and Google Chrome - older way by u/DefinitelyYou
- Add group policy templates to aid configuring in Chrome, Edge, and Firefox on Windows
Administrators can force specific configurations to deploy uBlock Origin (uBO). See "Deploying uBlock Origin: configuration". This is the recommended way to pre-configure uBO. New standalone settings are getting added as per demand.
For Firefox, the setting can be configured in "Native manifests" and Policies. Refer to Mozilla documentation about "Managed storage manifests" and its location for the Native manifests approach. See Mozilla's policy template for the Policies approach. You can also consult this specific comment in uBO issue tracker.
For Chrome, see https://www.chromium.org/administrators/configuring-policy-for-extensions/.
Deprecated approach -- avoid if you can
At launch time, uBO will look for a setting named adminSettings, and if it exists, it will parse, extract and overwrite a user's settings with the administrator-assigned ones. Note that Chromium managed storage is not always ready on first browser start after change, and up to three restarts may be needed for settings to be applied to uBO, see #1547, #1608.
The content of adminSettings is pretty straightforward: configure uBO as you wish for your users, then create a backup using the "Backup to file" in the Settings pane. Now open this backup file using a text editor, and remove all entries you do not want to overwrite while taking care to end up with a valid JSON file (mind trailing commas, etc.). All the entries left are the ones that will become overwritten on the user's side.
For example, I created a backup file after having customized uBO and removed everything except for the "Color-blind friendly" setting to force that setting to be set on the user's side. Resulting text file:
{
"userSettings": {
"colorBlindFriendly": true
}
}
Now, this JSON object can be used as the value for adminSettings.
For managing Chrome via Google Workspace, you can use this apps-script to generate a policy JSON that will modify Trusted Sites for all designated users.
You can configure the content of the "Filter lists" tab by providing a custom version of the assets.json file.
In the assetsBootstrapLocation key, you must add the URL of the modified assets.json file.
Implementation: #2314
Here are issues related to the customization of settings for deployed uBO. There may be some advice in these that you find helpful: