1--- 2stage: none 3group: unassigned 4info: 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 5type: reference 6--- 7 8# Terms of Service and Privacy Policy **(FREE SELF)** 9 10An administrator can enforce acceptance of a terms of service and privacy policy. 11When this option is enabled, new and existing users must accept the terms. 12 13When enabled, you can view the Terms of Service at the `-/users/terms` page on the instance, 14for example `https://gitlab.example.com/-/users/terms`. 15 16## Enforce a Terms of Service and Privacy Policy 17 18To enforce acceptance of a Terms of Service and Privacy Policy: 19 201. On the top bar, select **Menu > Admin**. 211. On the left sidebar, select **Settings > General**. 221. Expand the **Terms of Service and Privacy Policy** section. 231. Check the **All users must accept the Terms of Service and Privacy Policy to access GitLab** checkbox. 241. Input the text of the **Terms of Service and Privacy Policy**. You can use [Markdown](../../markdown.md) 25 in this text box. 261. Click **Save changes**. 27 28For each update to the terms, a new version is stored. When a user accepts or declines the terms, 29GitLab records which version they accepted or declined. 30 31Existing users must accept the terms on their next GitLab interaction. 32If a signed-in user declines the terms, they are signed out. 33 34When enabled, it adds a mandatory checkbox to the sign up page for new users: 35 36 37 38<!-- ## Troubleshooting 39 40Include any troubleshooting steps that you can foresee. If you know beforehand what issues 41one might have when setting this up, or when something is changed, or on upgrading, it's 42important to describe those, too. Think of things that may go wrong and include them here. 43This is important to minimize requests for support, and to avoid doc comments with 44questions that you know someone might ask. 45 46Each scenario can be a third-level heading, e.g. `### Getting error message X`. 47If you have none to add when creating a doc, leave this section in place 48but commented out to help encourage others to add to it in the future. --> 49
