> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/integrations/communications-integrations/slack.md).

# Slack

Spara can update your team about live conversations with prospective customers in Slack.

{% hint style="info" %}
You must be a Manager- or Integrator-level user to manage third party integrations.
{% endhint %}

Navigate to the [Integrations](https://app.spara.co/organization/integrations) page by clicking on the [Settings](https://app.spara.co/organization) link in the left hand navigation bar.

Click the "Authorize" button. This will lead you through an OAuth authentication flow. There are no further steps necessary upon completing this flow. You should see that the integration is "Enabled" within Spara's Integrations page.

<figure><img src="/files/qDZTIEHiRTZRncU0pQS2" alt=""><figcaption></figcaption></figure>

### Step 2: Configure notifications

Once Slack is connected, choose which events notify Slack and where to send them from [**Settings > Notifications**](https://app.spara.co/organization/notifications). See [Notifications](/platform/settings/notifications.md).

## Permissions and data use

When you connect Slack, Slack's authorization screen lists the OAuth scopes Spara requests. As with any Slack app, the screen describes what each scope *could* allow; Spara's integration exists only to post notifications into the channel you choose.

<table data-full-width="true"><thead><tr><th>Scope</th><th>What it grants</th><th>Why Spara needs it</th></tr></thead><tbody><tr><td><code>chat:write</code></td><td>Post messages</td><td>Send notifications into the channel you configure.</td></tr><tr><td><code>channels:read</code>, <code>groups:read</code></td><td>View basic info about public and private channels</td><td>List your channels so you can pick one during setup.</td></tr><tr><td><code>channels:join</code></td><td>Join public channels</td><td>Add the Spara bot to the channel you select so it can post there.</td></tr><tr><td><code>channels:manage</code></td><td>Create and manage public channels</td><td>Create the notification channel for you if it doesn't already exist.</td></tr><tr><td><code>users:read</code>, <code>users:read.email</code></td><td>View people in the workspace and their email addresses</td><td>Match notifications to the right sales rep.</td></tr></tbody></table>

### What Spara will and will not do

**Spara will:**

* Post automated notifications into the channel you explicitly configure.
* List your channels and workspace members so you can complete setup.
* Maintain an authenticated connection to deliver those notifications.

**Spara will not:**

* Read, store, analyze, or export your Slack messages. Spara requests no message-history scope, so it cannot read channel or direct-message history.
* Access channels outside of what you configure.
* Monitor, surveil, or index any Slack conversations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spara.com/integrations/communications-integrations/slack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.