# Notifications overview

Notifications are a key way for teams to stay in sync and collaborate more efficiently during a release process. Where before you might have been checking in various tools for status updates ([Is that build finished](https://docs.runway.team/types-of-notifications#release-cycle-1)? [Who's in charge of the next release](https://docs.runway.team/types-of-notifications#release-cycle)?), or pinging teammates when a task needed to be done ([did we get signoff from Compliance](https://docs.runway.team/types-of-notifications#release-cycle-2)?), Runway has you covered.

## Notifications settings

### Primary channel

All notifications will go to your primary channel, unless an override is defined in an individual notification's settings.

#### Configure primary channel

Visit your [Notifications](https://docs.runway.team/integrations/notifications) integration settings to configure your primary channel:

* [Slack](https://docs.runway.team/integrations/notifications/slack#connect-slack)
* [MS Teams](https://docs.runway.team/integrations/notifications/microsoft-teams)

### Configuring individual notifications

#### Navigate to notifications settings

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Notifications** in the sidebar

Settings for individual notifications

* **Enabled:** Toggle this type of notification on or off
* **Mentions:** Mention individual users or groups in the notification
* **Channel(s)** — Select or enter one or more channel names for this type of notification
  * Leave this field blank to send notifications to your configured [primary channel](#primary-channel) (default)
* **Custom text** — Include any additional information or instructions in this type of notification. This field supports [pattern token strings](https://docs.runway.team/getting-started/pattern-strings-tokens), allowing the custom copy to be dynamic

<figure><img src="https://727226624-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MjFmyReUsbJqDjHEAlW%2Fuploads%2FwlDv3KdC3eWCVf9zpVmR%2FScreenshot%202026-01-28%20at%201.42.07%E2%80%AFPM.png?alt=media&#x26;token=fde098e1-37e7-4894-be5d-6b176b1242f4" alt="Customizing notifications"><figcaption><p>Customizing notifications</p></figcaption></figure>

{% hint style="info" %}
Runway can send notifications to a **private** Slack channel once it has access to the channel, via one of these methods:

* In Slack, send a message to the private channel using the @Runway Slack handle
* In Slack, click on the user count icon at the top right of the private channel, then **Integrations** > **Add an app**. Search for Runway and click **Add**

Once the Runway app has been added, return to Runway, and the private channel name will now be available as an option in Runway integration settings for Slack.
{% endhint %}

{% hint style="info" %}
Release-specific channel names containing the pattern `{version}` are supported. If the [Create release-specific channel(s)](https://docs.runway.team/automations/types-of-automations#create-release-specific-channel-s) automation is enabled, Runway will automatically create a new Slack or Teams channel(s) for the release according to the entered pattern, if it doesn't exist yet. When Runway creates a channel, any notifications that reference it will include a direct link — so you can jump to the channel straight from the notification.
{% endhint %}

{% hint style="info" %}
You can also opt into receiving email notifications for each app-level notification type. For more details visit the [email notification settings documentation](https://docs.runway.team/using-runway/user-settings#email-notification-settings).
{% endhint %}

### Testing notifications&#x20;

Runway offers the ability to send a test DM notification to view a sample notification. Navigate to **Notification settings**, select the notification that you wish to test, and click "Send a test DM."&#x20;

{% hint style="info" %}
This functionality may not be available for all notifications, such as **Weekly user reviews issues digest**, **Phased release complete**, **Review submission item added**, and **Review submission item removed**.&#x20;
{% endhint %}