> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openlayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack notifications

> Route workspace and project events to Slack channels with destinations, so each channel gets only the updates its team needs.

Slack notifications are configured **team-wide** with destinations. A
destination is a Slack channel plus the events it receives, so you can send test
failures to an on-call channel and project activity to a broader one.

## Prerequisites

* Slack connected to your workspace. See the [Slack integration
  guide](https://docs.openlayer.com/integrations/slack.md). You add your first destination right after
  connecting.
* The **Admin** role to add, edit, pause, or remove destinations. Other roles
  can view them.

## Destinations

Destinations are listed under **Workspace settings** → **Notifications**. Each
destination has:

* **Channel** — the Slack channel that receives the messages.
* **Events** — the events the channel receives, grouped into workspace,
  general, development, and monitoring events.
* **Conditions** — optional **Status** and **Priority** filters on test result
  events (**Tests updated** under Development and under Monitoring). **Tests
  updated** under Monitoring matches **Failed** and **Errored** results by
  default, so skipped results stay out of the channel unless you add them.
* **Projects** — the projects that post to the channel, and whether projects
  created later are included automatically. Choose at least one project, or
  include projects created later.

A destination's channel can't change after you save it. To post to another
channel, add a new destination. To stop a destination for a while without
losing its setup, pause it instead of deleting it.

**Frameworks and rules changed**, **Project governance updated**, and **Project
updated** are off for Slack by default. Add them to a destination to send
governance and project activity to its channel. See [What the App tab
records](https://docs.openlayer.com/notifications/in-app.md#what-the-app-tab-records) for what they cover.

Events addressed to one person, such as **Tagged in comment**, **Lifecycle
review requested**, **Assigned to you**, and **Member role changed**, never go
to a channel. Members receive them [in-app](https://docs.openlayer.com/notifications/in-app.md) and by
[email](https://docs.openlayer.com/notifications/email.md).

If your workspace used the **General** and **Per project** Slack settings, they
carry over as destinations automatically. Per-project choices become a
destination scoped to those projects.

## What the messages look like

* Test results are grouped into one message per project per run, such as "2
  tests started failing in Chatbot". A message lists up to five tests, then "and
  N more".
* When a failing test recovers, Openlayer replies in the failure's thread
  instead of posting a new message.
* The **Weekly digest** posts one message per project every Monday.
* Each message has a **Manage notifications** link that opens your project
  subscriptions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.