2019-06-07 10:33:31 -04:00
---
type: howto
2020-07-17 20:09:34 -04:00
stage: Manage
2022-01-26 22:14:06 -05:00
group: Authentication and Authorization
2020-11-26 01:09:20 -05:00
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
2019-06-07 10:33:31 -04:00
---
2019-07-16 03:02:20 -04:00
2021-10-05 23:12:45 -04:00
# User email confirmation at sign-up **(FREE SELF)**
2016-05-06 16:59:45 -04:00
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
2021-08-26 05:11:15 -04:00
1. On the top bar, select **Menu > Admin** .
2021-06-15 14:09:57 -04:00
1. On the left sidebar, select **Settings > General** (`/admin/application_settings/general`).
1. Expand the **Sign-up restrictions** section and look for the **Send confirmation email on sign-up** option.
2019-06-07 10:33:31 -04:00
2021-06-07 02:10:26 -04:00
## Confirmation token expiry
By default, a user can confirm their account within 24 hours after the confirmation email was sent.
After 24 hours, the confirmation token becomes invalid.
2019-06-07 10:33:31 -04:00
<!-- ## 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. -->
