Shared Channels
A shared channel is a discussion channel opened jointly with another workspace you trust. Both sides post into one unified thread from their own workspace. It's built for B2B-style collaboration — vendor + customer support, cross-org partnerships, or separate business units in one company — without falling back to email or Slack.
Two sides: creator and partner
The workspace that opens the channel is the creator; the other is the partner.
Creator. In the New channel dialog, choose With a trusted workspace. You pick the partner (from the workspaces you trust) and set two names: an Internal name (how the channel appears in your own sidebar) and an External name (how it appears in the partner's sidebar). The channel then lives under Shared by us in your sidebar. The creator can post, rename (both names, side by side), and archive the channel.
Partner. The same channel appears under Shared with us in the partner's sidebar, in real time. The partner can post and read, and sees the per-side name the creator set. The partner cannot rename or archive the channel — the creator owns its lifecycle.
Who sent what
Every message records the workspace it was sent from. When a message comes from the other side, a small attribution chip with that workspace's name appears next to the author, so it's always clear who is speaking — even for a person who belongs to both workspaces.
The trust model
Trust is one-way and enough: to open a shared channel with workspace B, your workspace A must have B in its trusted list. B does not need to trust A. You manage your own trusted list in Workspace Settings → Trusted Workspaces.
| Situation | Result |
|---|---|
| A trusts B (B doesn't trust A) | A can open a shared channel with B; B can't with A |
| Mutual trust | Either side can open channels; each owns the ones it creates |
| No trust either way | Neither can open a shared channel |
To stop future invites from a workspace, remove it from your trusted list. To end an existing shared channel, the creator archives it — which removes it from the partner's sidebar too.
Privacy boundaries
Shared channels deliberately limit cross-workspace data exposure. When an agent is mentioned in a shared channel:
- the run is scoped to the channel's own messages — the agent cannot read either side's wider docs, notes, or tasks;
- it runs as, and is billed to, the caller's workspace;
- agents have no tools in shared channels by default;
- mentioning an agent that exists only in the other workspace renders as plain text.
In short, a customer asking a question in a vendor's shared channel never surfaces the vendor's unrelated internal knowledge.