> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/soda-documentation/integrations/slack.md).
# Slack
Configure Soda Cloud to connect your account to Slack so that you can:
* Send [notifications](/soda-documentation/manage-issues/notifications.md) for failed or warning check results to Slack channels
* Start conversations to track and resolve [data quality incidents](/soda-documentation/manage-issues/incidents.md) with Slack channels
## Configure a Slack integration
{% hint style="warning" %}
Only users with the **Manage Notification Rules** permission can create or edit rules. All users can view rules. Read about [Global and Dataset Roles](/soda-documentation/organization-and-admin-settings/global-and-dataset-roles.md)
{% endhint %}
{% stepper %}
{% step %}
In Soda Cloud, navigate to **your avatar** > **Organization Settings**, then navigate to the **Integrations** tab and click the **+** icon to add a new integration.
{% endstep %}
{% step %}
Choose **Slack** and proceed
{% endstep %}
{% step %}
Follow the guided steps to authorize Soda Cloud to connect to your Slack workspace. If necessary, contact your organization’s Slack Administrator to approve the integration with Soda Cloud.
{% endstep %}
{% endstepper %}
## Edit integration settings
You can edit the Slack-Soda integration by clicking on "**â‹®**" > **Edit integration settings**
### Configuration tab
Select the public channels to which Soda can post messages; Soda cannot post to private channels.
Note that Soda caches the response from the Slack API, refreshing it hourly. If you created a new public channel in Slack to use for your integration with Soda, be aware that the new channel may not appear in the **Configuration** tab in Soda until the hourly Slack API refresh is complete. You can manually trigger a refresh by clicking the **Update now** button.
### Scope tab
Select the Soda features (alert notifications and/or incidents) that can access the Slack integration.
### About integration scopes
#### Integration for alert notifications
You can use this integration to enable Soda Cloud to send alert notifications to a Slack channel to notify your team of **warn** and **fail** check results.
With such an integration, Soda Cloud enables users to select a Slack channel as the destination for an alert notification of an individual check or checks that form a part of an agreement, or multiple checks.
> To send notifications that apply to multiple checks, see [Notifications](/soda-documentation/manage-issues/notifications.md).
#### Integration for Soda Cloud incidents
You can use this integration to notify your team when a new incident has been created in Soda Cloud. With such an integration, Soda Cloud displays an external link to an incident-specific Slack channel in the **Incident Details**.
> Read more about [incidents](/soda-documentation/manage-issues/incidents.md).
***
{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/soda-documentation/reference/documentation-access-and-licensing.md).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.soda.io/soda-documentation/integrations/slack.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
