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

# Slack and Discord

> Connect Slack or Discord to Custory, link personal accounts, and understand what the integration enables.

Use this page when you want Slack or Discord connected to Custory for notifications, DMs, and thread-based AI workflows. This is the integration-level page, not the thread usage guide.

## What this integration does

Slack and Discord let Custory do three things:

* deliver notifications to channels and direct messages
* link a person's Slack or Discord identity to their Custory user
* support AI requests inside threads when you mention Custory

## Why it matters

If your team already works in Slack or Discord, this keeps Custory visible where the conversation is happening. You do not have to copy context into a separate tool just to get a response or a notification.

## What you need first

Before you connect either tool, make sure:

* the workspace has an active Slack or Discord integration
* the people who need DMs have linked their own Slack or Discord account
* the bot has access to the channel or thread where it should respond

## How it works

The integration has two layers:

1. Workspace connection
2. Personal account link

The workspace connection enables delivery and thread access. The personal link ties a Slack or Discord identity back to the right Custory user so permissions stay correct.

## Common uses

| Use case             | What Custory does                                               |
| -------------------- | --------------------------------------------------------------- |
| Slack or Discord DMs | Sends personal notifications to the linked account              |
| Channel delivery     | Posts workspace notifications where the team already works      |
| Thread AI            | Lets Custory read the active thread context and answer in place |

## Link your account

Use [Notifications](/notifications) to generate a link code and connect the personal account. That page owns the step-by-step DM setup.

## When to use this page

Use this page when you need the connection itself:

* to check whether Slack or Discord is available in the workspace
* to understand what the integration unlocks
* to see where the personal account link fits
* to jump to notifications or thread behavior after setup

## What good looks like

A healthy setup usually has:

* one active workspace integration per tool
* linked personal accounts for the people who need DMs or thread actions
* clear channel access for the bot
* notifications and thread workflows routed to the right place

## Next step

Read [Notifications](/notifications) for DM setup and delivery behavior, or read [Slack/Discord threads](/slack-discord-ai-threads) if you want to use Custory inside chat threads.