diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-25 23:30:46 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-25 23:30:46 +0300 |
commit | 1d287b31040662f1cc53a61b866ea97931a6b850 (patch) | |
tree | 64c1ff71f40695c1d516a7b24cabf06c408685f1 /doc/user/admin_area/settings/floc.md | |
parent | fdcb3d47df0526a9dc437c847683df8aae1e5d58 (diff) |
Add latest changes from gitlab-org/gitlab@13-12-stable-ee
Diffstat (limited to 'doc/user/admin_area/settings/floc.md')
-rw-r--r-- | doc/user/admin_area/settings/floc.md | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/doc/user/admin_area/settings/floc.md b/doc/user/admin_area/settings/floc.md new file mode 100644 index 00000000000..e1d10727341 --- /dev/null +++ b/doc/user/admin_area/settings/floc.md @@ -0,0 +1,40 @@ +--- +stage: none +group: unassigned +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments +--- + +# Federated Learning of Cohorts (FLoC) **(FREE SELF)** + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60933) in GitLab Free 13.12. + +Federated Learning of Conhorts (FLoC) is a feature that the Chrome browser has +rolled out, where users are categorized into different cohorts, so that +advertisers can use this data to uniquely target and track users. For more +information, visit the [FLoC repository](https://github.com/WICG/floc). + +To avoid users being tracked and categorized in any GitLab instance, FLoC is +disabled by default by sending the following header: + +```plaintext +Permissions-Policy: interest-cohort=() +``` + +To enable it: + +1. Go to the Admin Area (**{admin}**) and select **Settings > General**. +1. Expand **Federated Learning of Cohorts**. +1. Check the box. +1. Click **Save changes**. + +<!-- ## Troubleshooting + +Include any troubleshooting steps that you can foresee. If you know beforehand what issues +one might have when setting this up, or when something is changed, or on upgrading, it's +important to describe those, too. Think of things that may go wrong and include them here. +This is important to minimize requests for support, and to avoid doc comments with +questions that you know someone might ask. + +Each scenario can be a third-level heading, e.g. `### Getting error message X`. +If you have none to add when creating a doc, leave this section in place +but commented out to help encourage others to add to it in the future. --> |