Deployment & Managed Config - FrostCo/AdvancedProfanityFilter GitHub Wiki

Advanced Profanity Filter supports Managed Policies for centralized configuration.

Supported Environments

Currently managed configuration/policy is only supported on Google Chrome. Depending on demand, additional browser support may follow in the future.

Build Desired Config/Policy

1. Open the extension's Options page
2. Configure the extension to fit your needs (settings, words, etc.)
3. From the Options page, open the JavaScript console in the browser's "Dev Tools" (Right-click > Inspect)
4. In the JavaScript console run the following:

   managedConfig = true;
   

   • Note: This variable won't stay around, so either set it to false or refresh the page to revert back to normal
5. Navigate to the Config tab to get your config in the Managed Policy format that you can import into the Google Admin Console. Clicking on the "Export" button will save it to a file, or you can use the "Inline editor" to view the config on the page.

Additional Options

There are a few special options available for managed configuration/policy use:

• _managed: Choose level of restriction for managed config
  • 0: None - No managed storage, not applicable/useful when using managed storage
  • 1: Defaults - Provide default values but allow everything to be changed (WIP)
  • 2: Partial - lock values for provided keys, others can be changed (WIP)
  • 3: All - Lock all values to provided keys or defaults, no changes allowed
• _openOptionsOnInstall: Control whether the extension's Options page should be opened on installation
  • true: Open the extension's Options page on installation (default)
  • false: Do not open the extension's Options page on installation (default)