See the complete route index at https://crusible.dev/llms.txt before following links.

# Slack

What a Slack bridge is for: relaying a channel's conversation both ways with an origin badge, and leaving the record in Crusible. Not a provider.

<!-- https://crusible.dev/docs/reference/bridges/slack/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


Slack is <a class="docs-term" href="/docs/reference/glossary/#bridged">bridged</a>, not
<a class="docs-term" href="/docs/reference/glossary/#connected">connected</a>. Messages relay both ways
with an <a class="docs-term" href="/docs/reference/glossary/#origin-badge">origin badge</a>, and the
<a class="docs-term" href="/docs/reference/glossary/#record">record</a> stays in Crusible.

## Why the distinction matters

A <a class="docs-term" href="/docs/reference/glossary/#provider">provider</a> sits behind a
<a class="docs-term" href="/docs/reference/glossary/#surface">surface</a> and holds that surface's data.
A bridge sits on the <a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a>
itself, which is not a swappable surface. So the two words point at different
things, and reading one as the other leads to a wrong answer about the record:
a bridged Slack channel does not make Slack the authority for what was decided
in that channel.

## The badge is deliberate

Relayed content is marked wherever it appears — in the channel, in a thread,
in a search result. The badge is kept visible on purpose, because a
reader deciding whether a message is on the record needs to know where it came
from without asking.

## What a bridged channel is

It is an ordinary <a class="docs-term" href="/docs/reference/glossary/#channel">channel</a> whose
conversation is relayed. It has members, an
<a class="docs-term" href="/docs/reference/glossary/#agent">agent</a> roster, surfaces and a task board
like any other. People on the Slack side take part in the conversation; the
surfaces, and the work that happens on them, are reached in Crusible.

A partner organisation's shared channel works the same way and wears the same
kind of badge, so content from outside the workspace is always identifiable as
such.

## Where the bridge is set up

Slack appears in the **Integrations** pane of Settings, under **Communication**,
and an admin sets the bridge up there.
**Planned.** That pane carries no rows yet, so no bridge can be set up
today: it opens on a disabled **Coming soon**
control.
 That row is not a provider row: there is
no surface for Slack to sit behind, and there is no configuration in which a
team's Slack messages become the record for a channel. Bridged and connected
are different modes with different record-holders, and Slack is only ever the
first. Removing the bridge later stops the relay and leaves both sides intact:
the channel keeps everything already in its conversation, and Slack keeps its
own messages.