Notifications feature allows users to choose which team members will also receive an email when a deployment is performed using Compare and deploy to specific connections (target environments) - and these connections can configured on the account Notifications page:

Target connection can be a Salesforce org (individual org or a team-shared one), or your Version Control System (a Git branch).

Any settings that you have previously configured (prior to Gearset releasing the Notifications feature) will appear under All my other connections option.
​

If you're interested in having more flexibility and granularity, as well as transparency across your Gearset team, around configuring notifications for manual deployments and validations, then setting up notifications for other team members than the person (team member) executing a deployment is a useful step forward.

We offer you an ability to notify team members on manual deployments (which means this feature doesn't support automated CI jobs) to specific Salesforce org or Version Control System connections.

For example, you may want to notify another team member about all of your deployments to UAT org.

To add a new notifications for a specific deployment connection, on your Notifications page select Add notification.

You'll see below Add notification rule pop up window:

Under Connection type you can choose from the drop down either: Salesforce connection, Source control or All my other connections.

Under Select connection choose either a Salesforce org, or a Version Control System connected to your Gearset account.

On below example, we've selected a Test1 org:

Next, decide when a notification is to be sent to another team member. You have three options - when the deployment Succeeds or fails, Succeeds, or when it Fails.

Next you can look up team members on your team to whom you want email notifications to be sent.

Once added to the list, the names of team members will show up as on image below.

Note: We have two other helpful resources with information on how to add Gearset notifications to Slack or MS Teams channels.

Once you've configured everything, select Save.

You also have options to add Slack and/or MS Teams integration URLs.

When your notification is set up, it will be shown in the My connections / Team-shared connections tab - depending on whether you've set up a notification for an individual ora a team-shared org or VCS connection.

The notification we've added shows in My connections because it's been set up for an individual org:

By selecting this option (three dots):you also get access to either Edit or Delete your existing notification.

On the above screenshot, you see examples of other notifications apart from the notification we've gone through adding as part of this article.

For example, there is an email notification only for failed deployments to GitHub branches. We also have a notification for either successful or failed deployments to BitBucket branches.

At present, there are no granular restrictions that can be made to limit this functionality (e.g. if you only wanted team members to receive notifications after a commit to a specific branch within the repository).

If you have an org that has been delegated to you by another member on your Gearset team, consider that it may not be possible for you to add an email notification for that specific org.
​
As a workaround, we recommend that the member who delegated the org connection to you configures such notification directly on their Gearset account.