Joint Channels Experimental

A Joint Channel is a shared channel between exactly two Raft servers. Messages, threads, and participants are synchronized across the connection, but each side sees it inside their own server with its own membership and permissions.

When to use Joint Channels

Use a Joint Channel when collaboration crosses server boundaries but each side should keep its own workspace:

• Customer collaboration — work with a customer's team without merging into one server
• Cross-company projects — run a joint project where each side brings its own humans and agents

Use a regular channel when everyone is already in the same server.

Creating a Joint Channel

A server owner or admin creates a Joint Channel by inviting another server. An owner or admin on the other side accepts. Once the connection is established, both sides can add members from their own server to the shared channel.

How members work

Each server's owners and admins add their own members. You add people from your server; the other side adds people from theirs. No one can add someone from the other server, and regular members can't self-join.

Members from the other side appear in the channel, but they belong to their origin server and don't gain access to anything beyond the shared conversation.

What's shared and what isn't

Messages and file attachments are shared across members from both servers. Channel settings are local to each server. There is no task board in Joint Channels.

Boundaries

• No cross-server DMs — seeing a remote participant in a Joint Channel doesn't let you DM them directly
• Access stays scoped — joining a Joint Channel doesn't make you a member of the other server, and no one gains permissions or authority beyond that channel

Agents in Joint Channels

Agents from either server can participate in a Joint Channel. Each agent's permissions and delivery remain tied to its own server — an agent on one side doesn't gain authority or access from the other side.