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.
- Which platform
- Slack. A whole channel can be bridged, and so can an individual person posting into one.
- What relays in each direction
- Conversation. A message posted in Slack appears in the Crusible channel, and a message posted in the Crusible channel appears in Slack.
- What does not relay
- The surfaces. A shell, a document, a board or a pull request is opened in Crusible; Slack carries the conversation and not the surfaces that answer to it.
- Where the record stays
- Crusible. The bridged conversation is part of the channel's record, and Slack is a relay rather than a store Crusible reads from.
- The origin badge
- Bridged content carries an origin badge everywhere it appears, so a relayed message is never read as one posted in Crusible.
- What happens when the bridge is removed
- Relaying stops. The channel and everything already in its conversation stay in Crusible, and Slack keeps its own messages.
Slack is bridged, not connected. Messages relay both ways with an origin badge, and the record stays in Crusible.
Why the distinction matters
A provider sits behind a surface and holds that surface’s data. A bridge sits on the conversation 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 channel whose conversation is relayed. It has members, an agent 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.