| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [View Raw Code] [Original HTTPS Page] |
System administrators can configure Privacy Badger on managed devices by setting up an enterprise policy.
You can find the full list of available settings in Privacy Badger's managed storage schema. Please let us know if you'd like to set something that isn't yet supported.
Warning
Note that Privacy Badger currently reads and applies settings from managed storage on startup. To see your policy take effect on a managed device, first restart that device's browser.
If your Privacy Badgers were installed from eff.org (not from AMO):
Review Chromium's Documentation for Administrators documents, in particular Configuring Apps and Extensions by Policy.
See below for platform-specific tips.
Policy entries live at the following registry path:
HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\pkehgijcmpdhfbdbbnkijodmdjhbjlgp\policy
Use REG_DWORD for boolean values.
For example, to prevent the new user welcome page from launching upon Privacy Badger installation, create a showIntroPage entry set to a REG_DWORD value of 0.
The following example JSON policy disables Privacy Badger on example.com. This means Privacy Badger will be disabled when you visit any example.com page.
This policy also prevents the new user welcome page from launching upon Privacy Badger installation.
{
"disabledSites": {
"Value": [
"example.com"
]
},
"showIntroPage": {
"Value": false
}
}Follow instructions here to add an extension policy via plist file. Use this plist file as a template, subtituting the extension ID for the ID of your locally installed Privacy Badger.
Same as Chrome on Windows but with a different registry path:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\3rdparty\Extensions\mkejgcgkdlddbggjhhflekkondicpnop\policy
| Back | FazBrowse Home | New Git URL |