This article explains how to configure an SMTP server in GitProtect.
Navigate to ⚙ Settings > E-mail notifications and click this tab to expand its settings.
Expand the E-mail server tab.
Specify the SMTP server configuration:
Enter the SMTP server IP address and SMTP port.
Enter the sender's e-mail address.
If the server requires authentication:
Check the Server requires authentication checkbox to display additional settings.
Enter the login and either select the password from the Password Manager or add a new one.
Optionally, send a test message to verify that the settings are correct.
Review your settings and click Save to finish the setup.
This article explains how to configure email notifications in GitProtect.
Login to GitProtect Management Service, go to ⚙ Settings > Email notifications and switch the toggle to enable them.
Click the Enable notifications tile to open the settings.
Expand the Recipients tab and select or enter the email addresses that should receive notifications.
Next, expand the Email notifications tab to configure additional settings, such as language and .
To finish the email notifications setup, review your settings and click Save.
Below is a list of available notification types:
Backup plan summary — a notification is sent immediately after the backup task is finished or if it cannot be started. You can specify which task notifications you want to receive:
Successfully finished tasks — notifies you about all successfully completed tasks.
Tasks finished with warnings — notifies you about all tasks completed with warnings.
Notifications can also be configured for individual backup plans—you don't have to enable them for all plans. If only certain plans should have notifications, enable them within the backup plan settings (Backup plan settings > Advanced settings > Edit > Email notifications).
Similarly, if you want to maintain general notification settings but exclude specific plans, you can do so in the plan’s edit mode. Disabling notifications for a plan means that no notifications will be sent for that plan.
Email notifications are also available for expiring personal access tokens (PAT) to prevent backup tasks from failing due to an expired PAT used for integrating an organization with a DevOps platform (or at least to minimize the time needed to resolve this issue).
This configuration is organization-specific and can be adjusted in GitProtect Management Service under DevOps > your organization (i.e., GitHub) > Edit > Email notifications.
Enter the email address(es) that should receive notifications.
Select the preferred notification language.
Check Expired Personal Access Token checkbox.
In GitProtect, keeping data storage within capacity limits is crucial for maintaining efficient and reliable backup operations. When a repository approaches its storage limit, the service administrator should receive timely notifications which include the storage name and type, current usage, and remaining available space.
Global settings:
Go to ⚙ Settings > Email notifications and click the Email notifications tab to expand it.
Scroll down to the bottom of the settings panel and switch the Storage capacity notification toggle to enable it.
Set the threshold at which the notification should be sent, then click Save.
Storage-specific settings:
Navigate to the Storages tab.
Select the specific storage and click the edit icon next to it.
In the storage settings, enable and configure the Storage capacity notification option and click Save. These settings will override the global configuration for this specific storage.
Canceled tasks — notifies you about all canceled tasks.
Tasks not started — notifies you about tasks that could not be started.
Restore verification summary — sent after the data restoration process is completed; includes a detailed summary.
Daily report — an aggregate summary of all backup tasks performed during the day, sent at a manually defined time.
SLA Reports — monthly summary of backup correctness for the protected environment.
Storage capacity notifications — alerts you when storage usage exceeds the defined limit.
This article explains how to configure Slack notifications in GitProtect.
Login to GitProtect Management Service, go to ⚙ Settings > Slack notifications and switch the toggle to enable them.
Click the Enable notifications tile to open the settings.
Expand the Webhook address tab and enter the webhook URL for the Slack channel that should receive notifications.
Click the Test button to send a test message to your channel. If everything works correctly, click Save to proceed.
Next, expand the Slack notifications tab to configure additional settings, such as language and .
To finish the email notifications setup, review your settings and click Save.
Below is a list of available notification types:
Backup plan summary — a notification is sent immediately after the backup task is finished or if it cannot be started. You can specify which task notifications you want to receive:
Successfully finished tasks — notifies you about all successfully completed tasks.
Tasks finished with warnings — notifies you about all tasks completed with warnings.
Canceled tasks — notifies you about all canceled tasks.
Tasks not started — notifies you about tasks that could not be started.
Restore verification summary — sent after the data restoration process is completed; includes a detailed summary.
Daily report — an aggregate summary of all backup tasks performed during the day, sent at a manually defined time.
SLA Reports — monthly summary of backup correctness for the protected environment.
Storage capacity notifications — alerts you when storage usage exceeds the defined limit.
To generate a webhook URL, open your Slack and proceed with the following steps:
Create your Slack app— pick a name, choose a workspace to associate your app with, and click Create App.
In the opened window, select the Incoming Webhooks feature and click the Activate Incoming Webhooks toggle to switch it ON.
Once incoming webhooks are enabled, the settings page will refresh and additional options will appear. Click Add New Webhook to Workspace, select a channel where you want to receive notifications and confirm by clicking Allow.
Slack will display the webhook URL—copy and paste it into the webhook field (⚙ Settings > Slack notifications > Webhook address) in GitProtect.
Click the Test button to send a test message to your channel. If everything works correctly, click Save to proceed.
In addition to e-mail and Slack, you can use any webhook-enabled portal to receive notifications from the GitProtect system. For webhooks, configuration is limited to providing the webhook URL— by default, the system sends reports for all completed backups. The POST request sent by GitProtect to the specified webhook URL contains details such as the plan ID, plan name, execution times, and other relevant information.
Login to GitProtect Management Service, go to ⚙ Settings and click Webhooks to open the settings.
Click Add new button at the bottom of the panel, enter the webhook URL and click Save to finish the setup.
