Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
25b522a5
Commit
25b522a5
authored
Jun 05, 2019
by
Russell Dickenson
Committed by
Marcia Ramos
Jun 05, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Edited `Terms of Service` for SSOT guidelines
parent
0552e248
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
32 additions
and
14 deletions
+32
-14
doc/user/admin_area/settings/terms.md
doc/user/admin_area/settings/terms.md
+32
-14
No files found.
doc/user/admin_area/settings/terms.md
View file @
25b522a5
---
type
:
reference
---
# Enforce accepting Terms of Service
# Enforce accepting Terms of Service
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18570)
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18570)
> in [GitLab Core](https://about.gitlab.com/pricing/) 10.8
> 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
## Configuration
When it is required for all users of the GitLab instance to accept the
To enforce acceptance of a Terms of Service and Privacy Policy:
Terms of Service, this can be configured by an admin on the settings
page:
![
Enable enforcing Terms of Service
](
img/enforce_terms.png
)
.
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**
.
The terms itself can be entered using Markdown. For each update to the
![
Enable enforcing Terms of Service
](
img/enforce_terms.png
)
.
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.
When an admin enables this feature, they will automattically be
For each update to the terms, a new version is stored. When a user accepts or declines the terms,
directed to the page to accept the terms themselves. After they
GitLab will record which version they accepted or declined.
accept, they will be directed back to the settings page.
## New
registration
s
## New
user
s
When this feature is enabled, a checkbox will be available in the
When this feature is enabled, a checkbox is added to the sign-up form.
sign-up form.
![
Sign up form
](
img/sign_up_terms.png
)
![
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,
...
@@ -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.
they will be asked to accept the terms on their next interaction.
If a user declines the terms, they will be signed out.
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. -->
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment