Edited `Terms of Service` for SSOT guidelines
This commit is contained in:
parent
0552e248c1
commit
25b522a50c
|
@ -1,29 +1,35 @@
|
|||
---
|
||||
type: reference
|
||||
---
|
||||
|
||||
# Enforce accepting Terms of Service
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18570)
|
||||
> in [GitLab Core](https://about.gitlab.com/pricing/) 10.8
|
||||
|
||||
An admin can enforce acceptance of a terms of service and privacy policy. When this option is enabled, new and existing users must accept the terms.
|
||||
|
||||
## Configuration
|
||||
|
||||
When it is required for all users of the GitLab instance to accept the
|
||||
Terms of Service, this can be configured by an admin on the settings
|
||||
page:
|
||||
To enforce acceptance of a Terms of Service and Privacy Policy:
|
||||
|
||||
1. Log in to the GitLab instance as an admin user.
|
||||
1. Go to **Admin Area > Settings > General**.
|
||||
1. Expand the **Terms of Service and Privacy Policy** section.
|
||||
1. Check the **Require all users to accept Terms of Service and Privacy Policy when they access
|
||||
GitLab.** checkbox.
|
||||
1. Input the text of the **Terms of Service and Privacy Policy**. Markdown formatting can be used in this input box.
|
||||
1. Click **Save changes**.
|
||||
1. When you are presented with the **Terms of Service** statement, click **Accept terms**.
|
||||
|
||||
![Enable enforcing Terms of Service](img/enforce_terms.png).
|
||||
|
||||
The terms itself can be entered using Markdown. For each update to the
|
||||
terms, a new version is stored. When a user accepts or declines the
|
||||
terms, GitLab will keep track of which version they accepted or
|
||||
declined.
|
||||
For each update to the terms, a new version is stored. When a user accepts or declines the terms,
|
||||
GitLab will record which version they accepted or declined.
|
||||
|
||||
When an admin enables this feature, they will automattically be
|
||||
directed to the page to accept the terms themselves. After they
|
||||
accept, they will be directed back to the settings page.
|
||||
## New users
|
||||
|
||||
## New registrations
|
||||
|
||||
When this feature is enabled, a checkbox will be available in the
|
||||
sign-up form.
|
||||
When this feature is enabled, a checkbox is added to the sign-up form.
|
||||
|
||||
![Sign up form](img/sign_up_terms.png)
|
||||
|
||||
|
@ -49,3 +55,15 @@ If the user was already logged in when the feature was turned on,
|
|||
they will be asked to accept the terms on their next interaction.
|
||||
|
||||
If a user declines the terms, they will be signed out.
|
||||
|
||||
<!-- ## 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. -->
|
||||
|
|
Loading…
Reference in New Issue