Back to Wiki home

At the moment, it is not possible to set through policies the filtering mode to Optimal or Complete. The reason is that uBOL uses optional host permissions, which require a user gesture for a host permission to be granted, as required by the Optimal or Complete filtering mode.

Related issue on Chromium issue tracker: https://issues.chromium.org/issues/374073122. Starring the issue may help its prioritization.

For more general information about configuring policy for extensions, see https://www.chromium.org/administrators/configuring-policy-for-extensions/.

Important: It can take long seconds at browser launch before uBOL is able to read managed settings, and as a consequence there might be a delay at browser launch before they become effective and reflected in the user interface. This is out of control of uBOL. As soon as the storage.managed.get API returns, the managed settings should then be properly enforced.

Disable first-run page.

Value: Boolean.

Example of usage (Chromium on GNU/Linux):

    {
      "3rdparty": {
        "extensions": {
          "ddkjiahejlhfcafbddmgiahcphecmpfh": {
            "disableFirstRunPage": true
          }
        }
      }
    }

Disable uBOL for specific sites.

Value: Array of strings.

Each string is a hostname to add to the list. You can remove specific hostname from the no-filtering list by prefixing with -, e.g. -example.com. To remove all entries from the no-filtering list, use -*.

Example of usage (Chromium on GNU/Linux):

    {
      "3rdparty": {
        "extensions": {
          "ddkjiahejlhfcafbddmgiahcphecmpfh": {
            "noFiltering": [ "example.com", "mycorp.test" ]
          }
        }
      }
    }

Enable/disable specific rulesets.

Value: Array of strings.

Each string is the prefix + to enable or - to disable, followed by the id of the ruleset to enable/disable. The special value -* can be used to disable all non-default rulesets, except for those enabled by the policy.

Rulesets specified in the policy can't be enabled/disabled by the user.

Refer to ruleset-details.json to find out the id of a specific ruleset.

Mind the maximum number of enabled rulesets imposed by the extension framework.

Example of usage (Chromium on GNU/Linux), all rulesets except the default one(s) are disabled, "AdGuard URL Tracking Protection" and "EasyList/uBO – Cookie Notices" are enabled. +default is added so as to prevent the user from being able to disable it.

    {
      "3rdparty": {
        "extensions": {
          "ddkjiahejlhfcafbddmgiahcphecmpfh": {
            "rulesets": [
              "-*",
              "+default",
              "+adguard-spyware-url",
              "+annoyances-cookies"
            ]
          }
        }
      }
    }

Disable specific user-facing features.

Value: Array of strings.

Each string is a token which dictates what must be disabled. Currently supported tokens:

• dashboard: Prevent changes to any setting through the dashboard.
• filteringMode: Prevent changes to either default or per-site filtering mode.

Example of usage (Chromium on GNU/Linux):

    {
      "3rdparty": {
        "extensions": {
          "ddkjiahejlhfcafbddmgiahcphecmpfh": {
            "disabledFeatures": [ "dashboard" ]
          }
        }
      }
    }

People who know how to manage those settings under other OSes are welcome to contribute their knowledge here for the benefit of others, feel free to add useful information.

See related issue /~https://github.com/uBlockOrigin/uBOL-home/discussions/35.