Share Conversation

An agent conversation menu in the Hub offers two ways to take content out of the screen: Share, which prepares a read-only page, and Export, which creates a local file. Public sharing has a critical limitation in the current product and must not be treated as a completed publication.

Public link unavailable to visitors

The modal says that anyone with the link will be able to view the conversation, but a visitor without a login cannot load it today. The route queries protected tables, and the token created when sharing is enabled is not part of the URL or the read operation. An external recipient will normally see Conversation not available.

Where to find the action

1. Open the Hub at /hub.
2. If collaborative navigation is enabled for your organization, select Agents in the left rail.
3. Find the conversation. The list may group it under Pinned, Today, This week, or Earlier.
4. Open the item’s action menu and select Share.

The action belongs to the Hub’s agent conversation list. Rooms, direct messages, and external conversations managed at /admin/conversations use different surfaces.

What the modal does

The Share conversation modal contains the Public sharing switch. When you enable it, the client:

1. sets is_shared to active;
2. generates a new internal share_token;
3. displays a link in the form <current-origin>/share-chat/<conversation-id>;
4. provides two icon-only buttons: copy the link and open it in another tab.

The link uses the conversation ID, not share_token. Its origin is the same origin where SquadOS is open; do not assume a fixed domain.

Button accessibility

The copy and open buttons currently have no text name or accessible label. Visually, the copy button comes first and the open-in-new-tab button comes second.

Current access behavior

The /share-chat/<conversation-id> page sits outside the login route guard, but it queries conversations and messages directly. Current policies for these tables grant reads through authentication, organization membership, or participation — not through the sharing token and not to the anonymous role.

In practice:

• an external visitor without a session cannot read the conversation;
• an authenticated member who already has access to the conversation may be able to open the page;
• the page still checks is_shared after it reads the conversation;
• share_token is stored but does not authorize or identify the read;
• there is no expiration, password, or view-count limit.

Do not send the link as public evidence, and do not consider the conversation delivered until you test access in the recipient’s actual context.

What the read-only page renders

When the read is authorized and is_shared is active, the page shows:

• the conversation title and, when available, the agent’s name and avatar;
• user and assistant messages in chronological order;
• Markdown in assistant replies;
• a provider icon when the message records a model;
• date and time, plus icon actions to copy or download each message.

The page has no composer. It also does not query attachments, agent steps, technical details, credits, or notes. See Chat Interface for the differences among Hub, public page, widget, and admin handling.

Disabling sharing

Open Share conversation again and turn off Public sharing. The client sets is_shared to inactive and clears the token.

The URL does not change because it contains the conversation ID. If you enable sharing again, a new internal token is created, but the same URL is displayed. Because the token is not used for reads today, this rotation does not create an independent link.

If the operation fails, the switch returns to its previous state and a notification shows the error. Do not assume access was revoked: reopen the modal and confirm that the switch is off. These success and error notifications are currently fixed in Portuguese even in the EN interface.

Alternative for sending the content

In the same conversation menu, Export offers Text (.txt) and PDF:

• Text (.txt) downloads all textual messages in order, including time, role, and model when available;
• PDF opens a new window and invokes the browser’s print dialog; it does not directly download a PDF.

Prefer TXT after reviewing the content, then share the file through your organization’s approved channel. The exporter currently fixes dates, roles, and document headings in PT-BR even in the EN interface.

Untrusted title and PDF export

Do not use the PDF option if the conversation title came from an untrusted source. The current print document inserts the title without escaping it. Rename and review the conversation before exporting, or use TXT.

Checklist before sending

• Review every message: sharing does not let you select only one excerpt.
• Do not create or send the file if any message contains credentials, personal data, or confidential information.
• Use TXT as the alternative until anonymous link access is fixed.
• Verify the final file and delivery channel; generating or copying something does not prove the recipient can access it.