Email

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

You can customize some of the content in emails sent from your GitLab instance.

Custom logo

The logo in the header of some emails can be customized, see the logo customization section.

Include author name in email notification email body

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

By default, GitLab overrides the email address in notification emails with the email address of the issue, merge request, or comment author. Enable this setting to include the author's email address in the body of the email instead.

Prerequisites:

• Administrator access.

To include the author's email address in the email body:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Select the Include author name in email notification email body checkbox.
5. Select Save changes.

Enable multipart email

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

GitLab can send email in multipart format (HTML and plain text) or plain text only.

To enable multipart email:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Select Enable multipart email.
5. Select Save changes.

Custom hostname for private commit emails

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

This configuration option sets the email hostname for private commit emails. By default it is set to users.noreply.YOUR_CONFIGURED_HOSTNAME.

To change the hostname used in private commit emails:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Enter the desired hostname in the Custom hostname (for private commit emails) field.
5. Select Save changes.

[!note] After the hostname is configured, every private commit email using the previous hostname is not recognized by GitLab. This can directly conflict with certain push rules such as Check whether author is a GitLab user and Check whether committer is the current authenticated user.

Custom additional text

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

You can add additional text at the bottom of any email that GitLab sends. This additional text can be used for legal, auditing, or compliance reasons, for example.

To add additional text to emails:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Enter your text in the Additional text field.
5. Select Save changes.

User deactivation emails

GitLab sends email notifications to users when their account has been deactivated.

To disable these notifications:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Clear the Enable user deactivation emails checkbox.
5. Select Save changes.

Custom additional text in deactivation emails

{{< history >}}

• Introduced in GitLab 15.9 with a flag named deactivation_email_additional_text. Disabled by default.
• Enabled on GitLab Self-Managed in GitLab 15.9.
• Generally available in GitLab 16.5. Feature flag deactivation_email_additional_text removed.

{{< /history >}}

You can add additional text at the bottom of the email that GitLab sends to users when their account is deactivated. This email text is separate from the custom additional text setting.

To add additional text to deactivation emails:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Enter your text in the Additional text for deactivation email field.
5. Select Save changes.

Group and project access token expiry emails to inherited members

{{< history >}}

• Notifications to inherited group members introduced in GitLab 17.7 with a flag named pat_expiry_inherited_members_notification. Disabled by default.
• Feature flag pat_expiry_inherited_members_notification enabled by default in GitLab 17.10.
• Feature flag pat_expiry_inherited_members_notification removed in GitLab 17.11

{{< /history >}}

In GitLab 17.7 and later, the following inherited group and project members can receive emails about group and project access tokens that are expiring soon, in addition to direct group and project members:

• For groups, members who inherit the Owner role for those groups.
• For projects, project members who inherit the Owner or Maintainer role for projects that belong to those groups.

To enable token expiration emails to inherited group and project members:

1. In the upper-right corner, select Admin.
2. Select Settings > Preferences.
3. Expand Email.
4. Under Expiry notification emails about group and project access tokens should be sent to:, select All direct and inherited members of the group or project.
5. Select the Enforce this setting for all groups on this instance checkbox.
6. Select Save changes.

For more information on token expiration emails, see:

• For groups, the group access token expiry emails documentation.
• For projects, the project access token expiry emails documentation.