2019-06-07 10:33:31 -04:00
|
|
|
---
|
|
|
|
|
type: howto
|
|
|
|
|
---
|
2019-07-16 03:02:20 -04:00
|
|
|
|
2016-05-06 16:59:45 -04:00
|
|
|
# User email confirmation at sign-up
|
|
|
|
|
|
2019-06-07 10:33:31 -04:00
|
|
|
GitLab can be configured to require confirmation of a user's email address when
|
2020-03-11 20:09:34 -04:00
|
|
|
the user signs up. When this setting is enabled, the user is unable to sign in until
|
|
|
|
|
they confirm their email address.
|
2016-05-06 16:59:45 -04:00
|
|
|
|
2020-02-10 07:08:59 -05:00
|
|
|
In **Admin Area > Settings** (`/admin/application_settings/general`), go to the section
|
2019-06-07 10:33:31 -04:00
|
|
|
**Sign-up Restrictions** and look for the **Send confirmation email on sign-up** option.
|
|
|
|
|
|
|
|
|
|
<!-- ## 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. -->
|
