supported_on is used for released platforms with milestone range while future_on is used for unreleased platforms. supported_on and future_on: They control the platforms that the policy supports.Please note that, all attributes below other than supported_on, future_on do not change the code behavior.

Please make sure you get the version and feature flags (such as dynamic_refresh and supported_on) right. This file contains meta-level descriptions of all policies and is used to generate code, policy templates (ADM/ADMX for Windows and the application manifest for Mac), as well as documentation.Declare the policy in the policy_templates.json.Negative policies ( Disable, Disallow) are verboten because setting something to “true” to disable it confuses people.Consider the foreseeable future and try to avoid conflicts with possible future extensions or use cases.Prefer “XXXEnabled” over “EnableXXX” because the former is more glanceable and sorts better. Choose a name that is consistent with the existing naming scheme.Think carefully about the name and the desired semantics of the new policy:.To read more about best practices for shipping enterprise friendly features read this article. Create a policy to give enterprise users more time to migrate away from the feature. Create a policy so that the admin can disable or enable the feature for all users.ĭeprecating an old feature. Here is the help center article that talks about Chrome policy and its deployment.

With different device management tools, an administrator can deliver these polices to many users.

These configurations are called policy and they give administrators more advanced controls than the normal users. Chrome exposes a different set of configurations to administrators.

Set google chrome homepage registry