Shared chats

Sharing a chat publishes a read-only snapshot of it at a link anyone in your organization can open. It is one gesture: Share copies the link to your clipboard, and you paste it wherever your team talks. The mechanic is light enough to use casually — share a question and its answer the way you would share a document.

Sharing a chat

Open the chat and click the ⋯ menu in the header, then Share. The link lands on your clipboard immediately — a Link copied toast confirms it. The same entry lives on each chat's row menu in the sidebar.

Two things worth knowing about the link:

• It is org-scoped. Only signed-in members of your organization can open it; it is not a public URL.
• It is a snapshot. The recipient sees the conversation as it stood when you shared it. If the chat moves on and you want to share the newer state, click Share again — the link stays the same and the snapshot refreshes.

What the viewer sees

The link opens a read-only Shared chat view: the transcript, with a byline naming who shared it and when. There is no composer — a shared chat is something to read, not a place to reply. A viewer who wants to take the topic further starts their own chat — or a task in a project, if what they want is a deliverable.

Stopping sharing

The chat's row menu offers Stop sharing once a chat is shared. The link stops working immediately; visitors land on a "no longer available" page. Deleting the chat has the same effect on the link. Sharing again later publishes a fresh snapshot.

Where this fits

Shared chats are the lightweight way to hand a conversation to a teammate without leaving the product. The heavier-weight alternative is bringing the teammate into a Project where chats, files, and agents are shared by default. Sharing is for one-off handoffs; a Project is for ongoing collaboration on the same work.