- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
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
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
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.
To include the author’s email address in the email body:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Select the Include author name in email notification email body checkbox.
- Select Save changes.
Enable multipart email
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
GitLab can send email in multipart format (HTML and plain text) or plain text only.
To enable multipart email:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Select Enable multipart email.
- Select Save changes.
Custom hostname for private commit emails
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
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:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Enter the desired hostname in the Custom hostname (for private commit emails) field.
- Select Save changes.
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
- Tier: Premium, Ultimate
- Offering: GitLab Self-Managed
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:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Enter your text in the Additional text field.
- Select Save changes.
User deactivation emails
GitLab sends email notifications to users when their account has been deactivated.
To disable these notifications:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Clear the Enable user deactivation emails checkbox.
- Select Save changes.
Custom additional text in deactivation emails
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
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:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- Enter your text in the Additional text for deactivation email field.
- Select Save changes.
Group and project access token expiry emails to inherited members
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
The availability of emails to inherited project and group members is controlled by a feature flag. For more information, see the 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:
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Preferences.
- Expand Email.
- 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.
- Select the Enforce this setting for all groups on this instance checkbox.
- 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.
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support