Skip to content
SquadOS SquadOS Docs

Share Conversation

Public sharing turns a Hub conversation into a read-only page accessible by link. Useful for sending an example of a support exchange to a colleague, showing off an interesting agent reply, or attaching evidence to a support ticket.

Where it is available

Section titled “Where it is available”

Sharing is available only for Hub conversations — the ones you had at /hub/chat. External conversations (public chat, widget, WhatsApp, Telegram, API) don’t have this option; to share them as evidence, use the admin panel directly or export through other channels.

Section titled “Generating a share link”
  1. Open the Hub (/hub/chat).
  2. In the left sidebar, hover the conversation you want to share and click the three-dot button.
  3. Click Share.
  4. In the Share conversation modal, turn on the Public sharing switch.
  5. Copy the link in the generated field, or click the “open in new tab” button to verify it.

The link looks like https://squados.io/share-chat/<conversation-id>. Anyone with the link can view the conversation, no login required.

Section titled “What shows up on the public link”
  • Conversation title.
  • Agent name and avatar.
  • All user and agent messages, in chronological order.
  • AI model used for each reply (provider icon).
  • Timestamp of each message.

What does NOT show up

Section titled “What does NOT show up”
  • Notes on the conversation — private, admin-only. See Internal Notes.
  • Personal data of the conversation owner (email, profile, organization).
  • Who actually replied during a human intervention — to a public viewer, all assistant messages appear to come from the agent.
  • Credit usage and technical execution details.
Section titled “Link security”

Access is controlled by the conversation’s is_shared flag, not by the URL. Important points:

  • The URL contains the conversation ID, a UUID v4. Not realistically guessable by brute force, but also not a cryptographic secret — treat the link as public to anyone who has it.
  • Whoever you send the link to can forward it. There’s no authentication on the public page.
  • Sharing is per conversation, not per agent — enabling share on one conversation doesn’t affect others.
  • The backend validates the flag on every access. If you revoke, the link stops working immediately — even if someone had the URL saved.

Revoking access

Section titled “Revoking access”
  1. Open the Share conversation modal again.
  2. Turn off the Public sharing switch.

From that moment, anyone trying to open the link sees “This conversation is not available”. If you re-enable later, the same URL starts working again — a different URL is not generated. If that’s a concern, avoid re-enabling share on conversations with sensitive content.

Good practices

Section titled “Good practices”
  • Review the conversation before sharing. Look for personal data, credentials, or confidential info that might have been pasted into the chat.
  • Prefer screenshots for short excerpts — they expose less than releasing the entire conversation.
  • Revoke after using. Share links stay live indefinitely; turn them off when you no longer need them.
  • For conversations with sensitive data, consider whether your organization’s privacy policy allows exposing the content via a public link.