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

# Slack

> Turn the channels and threads your team works in into shared workspace memory

Slack turns channels and threads into searchable memory. **Connect** on the Slack card ([Integrations](/cognee-cloud/ui/integrations) → **Data sources**) authorizes the Cognee Slack app for your workspace; a connected card shows the connection's status and channel health, and **Manage** — or **Reconnect**, when the connection needs attention — opens the same dialog.

## Choosing channels

Authorizing Slack reads nothing on its own: **ingestion is opt-in per channel**. The Manage dialog leads with the channels the bot can see, and you tick the ones to ingest, with a search box and bulk actions for a long list. Switching a channel on also ingests the history it already has.

Until channels are routed the card says which of the two states it is in:

| Card line | Meaning |
| - | - |
| **Not in any channel yet** | The Cognee bot has not been invited to a channel. Invite it in Slack first. |
| **No channels selected yet** | The bot is in channels, but none are routed into a dataset. |
| *3 of 12 channels syncing* | Channels are routed and reading. |
| **Channel list unavailable** | The channel list could not be read from Slack. |

Only the workspace owner can connect, manage, disconnect, or choose channels.

## Linking your own Slack account

Connecting Slack authorizes the workspace, not you personally. To have `/cognee-recall` in Slack answer as *you* — from what your own Cognee account can see — run **`/cognee-link`** in Slack. It replies with a link to **Connect your Slack account** (route `/link-slack`), where **Connect my account** completes the pairing. Each link is valid for **10 minutes**; when it expires or arrives malformed the page says so and tells you to run `/cognee-link` again.

The page refuses to pair the wrong things, since it can only see which Slack member is asking:

| Situation | What it says |
| - | - |
| The workspace has no Slack connection | *{workspace} has no Slack connection, so there is nothing to link your account to here.* Switch to the workspace your team connected Slack in, then reopen the link. |
| The link came from a different Slack workspace | *This link came from a different Slack workspace than the one connected to {workspace}.* Switch to the matching Cognee workspace at the top of the page, then reopen the link. |
| Done | *`/cognee-recall` in Slack now answers as you, from what your Cognee account can see*, with **Back to Integrations**. |

## Disconnecting

Disconnecting stops the reading. What Cognee already learned from the connection stays in memory — Slack's disconnect does not offer to delete it, unlike [Google Drive's](/cognee-cloud/company-brain/google-drive#disconnecting).

<Note>
  Self-hosted Cognee deployments run their own, separate Slack app against their own backend. Setup and usage are covered in the [Slack integration guide](/integrations/slack-integration), including importing selected channel and thread history with `/cognee-import`.
</Note>