Identity verification

Identity verification provides multiple layers of GitLab account security. Depending on your risk score, you might be required to perform up to three stages of verification to register an account:

• All users - Email verification.
• Medium-risk users - Phone number verification.
• High-risk users - Credit card verification.

By default, users provisioned with SAML or SCIM must complete email verification. You can bypass email verification by adding a custom domain. GitLab automatically confirms user accounts when their email domain matches.

If you encounter identity verification errors when running CI/CD pipelines, see debugging pipeline errors.

Email verification

To register an account, you must provide a valid email address. See Make new users confirm email.

Phone number verification

In addition to email verification, you might also be asked to provide a valid phone number and verify a one-time password (OTP) code.

Country support

Some countries have limited or no support for phone number verification:

• Unsupported: Phone verification is not available.
• Partial support: Phone verification might not work due to local regulations or enforcement policies.

If phone verification is unavailable in your country, try credit card verification or create a support ticket.

Credit card verification

In addition to an email address and phone number, you might also need to provide a valid credit card number to verify your account.

GitLab does not store your card details directly or make any charges. This process is not connected to any billing information for your groups.

You cannot verify an account with a credit card number associated with a banned user.