Skip to main content

Real-Time Conversation Sharing

RelayHub is built for teams. When you share a conversation with a teammate, they do not just see a static transcript — they see AI responses stream in live, as they are generated. Multiple people can watch and participate in the same conversation simultaneously over WebSocket connections. This makes RelayHub feel less like a personal chat tool and more like a shared workspace where your team can think together with AI.

How to Share a Conversation

1

Open the conversation you want to share

Navigate to the conversation in your sidebar and open it.
2

Click the Share button

Click the Share icon in the top-right corner of the chat. This opens the sharing panel.
3

Select teammates

Search for teammates by name or email. You can share with one person or multiple people at once. Only members of your organization appear in the search results.
4

Set permission level

For each person, choose their permission level: View Only or Can Respond. You can set different permissions for different people.
5

Confirm sharing

Click Share to send the invitation. Your teammates will see the shared conversation appear in their sidebar immediately.

Permission Levels

The teammate can see the full conversation history and watch new AI responses stream in live. They cannot send messages, change the model, or modify any chat settings. Use this when you want someone to observe or review without altering the conversation.
Anyone with Can Respond permission can change the AI model and settings for the conversation. Coordinate with your team to avoid unexpected changes mid-conversation.

What Real-Time Means

When a shared conversation has an active AI response, every participant sees it stream in simultaneously. There is no polling or refresh needed. This is powered by WebSocket connections that push updates instantly. Here is what each participant sees in real time:
EventWhat You See
Someone sends a messageThe message appears in your chat immediately
AI starts respondingTokens stream in live, same as if you sent the message yourself
Someone changes the modelYou see the new model reflected in the chat header
A file is attachedThe file attachment appears in the conversation for all participants
Real-time sharing is ideal for live demos, pair problem-solving, and team brainstorming sessions. One person can drive the conversation while others watch and discuss over a call.

Managing Shared Access

You can modify or revoke sharing at any time:
  • Change permissions — Reopen the sharing panel and adjust a teammate’s permission level from View Only to Can Respond, or vice versa.
  • Revoke access — Click the Remove button next to a teammate’s name in the sharing panel. They will lose access immediately and the conversation disappears from their sidebar.
  • See who has access — The sharing panel shows all current participants and their permission levels.
Revoking access does not delete any messages the person sent while they had Can Respond permission. Those messages remain in the conversation history.

Collaboration Best Practices

  • Assign one driver. In live sessions, designate one person to send messages to the AI. Multiple people sending competing messages can create a confusing conversation thread.
  • Use View Only by default. Share as View Only unless someone specifically needs to interact with the AI. This prevents accidental messages or setting changes.
  • Communicate outside the chat. RelayHub shows what happens in the conversation, but not sidebar commentary. Use your team’s messaging tool (Slack, Teams) alongside RelayHub for meta-discussion about the AI’s responses.
  • Delete sensitive conversations when done. Shared conversations persist until explicitly deleted. If the conversation contains sensitive information, clean it up when the collaboration is complete.

Who Can See Shared Conversations?

Only the people you explicitly share with can see the conversation. Sharing is not broadcast to your entire organization. Admins can see conversation metadata for auditing purposes but do not automatically have access to conversation content.