Allow enterprise extensions to use storage.managed to grant consent. (#…

…1785)

src/content/documentation/develop/best-practices-for-collecting-user-data-consents.md

@@ -5,8 +5,8 @@ permalink: /documentation/develop/best-practices-for-collecting-user-data-consen
 topic: Develop
 tags:
   [add-ons, extensions, how-to, privacy, ui, user-interface, ux, webextensions]
-contributors: [rebloor, hamatti]
-last_updated_by: hamatti
+contributors: [rebloor, hamatti, mkaply]
+last_updated_by: mkaply
 date: 2023-01-11
 ---
 
@@ -20,6 +20,9 @@ If your extension collects user data, it needs to comply with the requirement of
 
 A common developer question about these policies is how to translate them into browser extension features that are compliant to [Mozilla’s Add-on policies](/documentation/publish/add-on-policies/). This how-to is the result of those requests and offers advice on implementing prompts to meet the data collection and add-on policies. This article suggests how you can implement suitable prompts but it doesn’t replace or supersede the policies; you still need to confirm that your extension complies with the policies.
 
+Note: If your extension is installed in an enterprise via the `force_installed` or `normal_installed` options in the [ExtensionSettings enterprise policy](https://mozilla.github.io/policy-templates/#extensionsettings), you must still implement the disclosure and consent experience in the add-on.
+You can set a value via the [3rdparty enterprise policy](https://mozilla.github.io/policy-templates/#3rdparty) and read it with `storage.managed` in the add-on to determine if consent is granted. You must display the disclosure and consent experience if the value is not set in `storage.managed`.
+
 {% endcapture %}
 {% include modules/page-hero.liquid,
     content: page_hero_banner_content