Skip to content

Commit 1bfcedb

Browse files
authored
Updates for policy info move to Firefox administrator reference (#2261)
I reviewed the page and it looks good. Thanks @rebloor
1 parent 17e1f76 commit 1bfcedb

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ Firefox provides a built-in consent for data collection and transmission in Fire
2626
:::
2727

2828
::: note
29-
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.
30-
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`.
29+
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.
30+
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`.
3131
:::
3232

3333
{% endcapture %}

src/content/documentation/enterprise/enterprise-development.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,8 @@ As an extension developer, you may want to customize your add-on via policy or m
3131

3232
## Data collection disclosure and consent for enterprise extensions
3333

34-
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.
35-
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`.
34+
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.
35+
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`.
3636

3737
{% endcapture %}
3838
{% include modules/column-w-toc.liquid,

src/content/documentation/enterprise/enterprise-distribution.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The recommended alternative approach is to use the option for self-distributed a
6666

6767
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.
6868

69-
See [ExtensionSettings](https://mozilla.github.io/policy-templates/#extensionsettings) for details.
69+
See [ExtensionSettings](https://firefox-admin-docs.mozilla.org/reference/policies/extensionsettings/) for details.
7070

7171
{% endcapture %}
7272
{% include modules/one-column.liquid,

src/content/documentation/enterprise/enterprise-policies-that-impact-extensions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ date: 2019-08-12 05:01:39
1616

1717
# Enterprise policies that impact extensions
1818

19-
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).
19+
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/).
2020

2121
{% endcapture %}
2222
{% include modules/page-hero.liquid,

src/content/documentation/publish/distribute-for-desktop-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Of these options, directing the user to install from AMO is recommended. It avoi
3737

3838
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.
3939

40-
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.
40+
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.
4141

4242
{% endcapture %}
4343
{% include modules/one-column.liquid,

0 commit comments

Comments
 (0)