Please verify with a ChromeOS policy owner if your profile policy does not support dynamic refresh on ChromeOS. ChromeOS does not always support non-dynamic profile policies. It means the admin can change the policy value and Chrome will honor the change at run-time without requiring a restart of the browser. We strongly encourage developers to make their policies support this attribute.The setting needs an indicator to tell users that the setting is enforced by the administrator.PrefService:Preference::IsManaged reveals whether a prefs value comes from policy or not.If your feature can be controlled by GUI in chrome://settings, the associated option should be disabled when the policy controlling it is managed.Disable the user setting UI when the policy is applied.iOS platform has its own configuration_policy_handler_list_factory.mm and policy_test_cases.json file.Test the mapping by adding policy to policy_test_cases.json (see instructions).If the policy needs additional verification or processing, please implement a ConfigurationPolicyHandler to do so. Most policies can be mapped to prefs with kSimplePolicyMap in configuration_policy_handler_list_.We also strongly encourage developers to register the prefs with Profile Prefs if possible, because this gives admin more flexibility of policy setup. Please note that, this must match the per_profile attribute in the policy_templates.json. ![]() Create a prefs and register the prefs in Local State or Profile Prefs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |