diff --git a/src/content/documentation/develop/best-practices-for-collecting-user-data-consents.md b/src/content/documentation/develop/best-practices-for-collecting-user-data-consents.md index 0e329ca0d..a5c1e801f 100644 --- a/src/content/documentation/develop/best-practices-for-collecting-user-data-consents.md +++ b/src/content/documentation/develop/best-practices-for-collecting-user-data-consents.md @@ -26,8 +26,8 @@ Firefox provides a built-in consent for data collection and transmission in Fire ::: ::: 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`. +If your extension is installed in an enterprise via the `force_installed` or `normal_installed` options in the [ExtensionSettings enterprise policy](https://firefox-admin-docs.mozilla.org/reference/policies/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://firefox-admin-docs.mozilla.org/reference/policies/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 %} diff --git a/src/content/documentation/enterprise/enterprise-development.md b/src/content/documentation/enterprise/enterprise-development.md index 498387f87..9c9ddb429 100644 --- a/src/content/documentation/enterprise/enterprise-development.md +++ b/src/content/documentation/enterprise/enterprise-development.md @@ -31,8 +31,8 @@ As an extension developer, you may want to customize your add-on via policy or m ## Data collection disclosure and consent for enterprise extensions -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`. +If your extension is installed in an enterprise via the `force_installed` or `normal_installed` options in the [ExtensionSettings enterprise policy](https://firefox-admin-docs.mozilla.org/reference/policies/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://firefox-admin-docs.mozilla.org/reference/policies/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/column-w-toc.liquid, diff --git a/src/content/documentation/enterprise/enterprise-distribution.md b/src/content/documentation/enterprise/enterprise-distribution.md index a7f25f1c8..4e8d41cb8 100644 --- a/src/content/documentation/enterprise/enterprise-distribution.md +++ b/src/content/documentation/enterprise/enterprise-distribution.md @@ -66,7 +66,7 @@ The recommended alternative approach is to use the option for self-distributed a This is the recommended approach to installing add-ons automatically. The ExtensionSettings policy enables you to set default behavior for the browser and installation behavior for extensions. For example, you could disable extension installation generally, then automatically install or allow installation of specific extensions. -See [ExtensionSettings](https://mozilla.github.io/policy-templates/#extensionsettings) for details. +See [ExtensionSettings](https://firefox-admin-docs.mozilla.org/reference/policies/extensionsettings/) for details. {% endcapture %} {% include modules/one-column.liquid, diff --git a/src/content/documentation/enterprise/enterprise-policies-that-impact-extensions.md b/src/content/documentation/enterprise/enterprise-policies-that-impact-extensions.md index b21a9bca7..6b0d6a149 100644 --- a/src/content/documentation/enterprise/enterprise-policies-that-impact-extensions.md +++ b/src/content/documentation/enterprise/enterprise-policies-that-impact-extensions.md @@ -16,7 +16,7 @@ date: 2019-08-12 05:01:39 # Enterprise policies that impact extensions -Policies enable you to control the capabilities of Firefox. This article summarizes the policies that affect the installation, behavior, and update of web extensions. For a full list of policies, see [mozilla/policy-templates](https://github.com/mozilla/policy-templates) on GitHub. For details on how to implement policies, see [Manage settings via policy](https://support.mozilla.org/products/firefox-enterprise/policies-customization-enterprise/manage-settings-policy). +Policies enable you to control the capabilities of Firefox. This article summarizes the policies that affect the installation, behavior, and update of web extensions. For a full list of policies, see the [Firefox administrator reference ](https://firefox-admin-docs.mozilla.org/reference/policies/). For details on how to implement policies, see [Configuring policies](https://firefox-admin-docs.mozilla.org/guides/policies-configuration/). {% endcapture %} {% include modules/page-hero.liquid, diff --git a/src/content/documentation/publish/distribute-for-desktop-apps.md b/src/content/documentation/publish/distribute-for-desktop-apps.md index b0008aa2a..2b3dfaeac 100644 --- a/src/content/documentation/publish/distribute-for-desktop-apps.md +++ b/src/content/documentation/publish/distribute-for-desktop-apps.md @@ -37,7 +37,7 @@ Of these options, directing the user to install from AMO is recommended. It avoi If you would like to direct users to install the add-on from your website, please read this article on [self-distribution](/documentation/publish/submitting-an-add-on/#self-distribution) to learn how to prepare the `.xpi` file for web installs. -Enterprise administrators and people who distribute their builds of Firefox (such as some Linux and Selenium distributions) can continue to deploy extensions to users. Enterprise administrators can do this using [policies](https://github.com/mozilla/policy-templates#extensionsettings). Additionally, Firefox Extended Support Release (ESR) continues to support sideloading as an extension installation method. +Enterprise administrators and people who distribute their builds of Firefox (such as some Linux and Selenium distributions) can continue to deploy extensions to users. Enterprise administrators can do this using [policies](https://firefox-admin-docs.mozilla.org/reference/policies/extensionsettings/). Additionally, Firefox Extended Support Release (ESR) continues to support sideloading as an extension installation method. {% endcapture %} {% include modules/one-column.liquid,