> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/share-a-conversation.md).

# Share a conversation

Conversation sharing provides a link to a saved conversation, subject to the interface’s access mode. Export creates a separate copy in the format provided by the interface. Review the access behavior below before distributing either.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fpakwu8X74xsqySIWkXKq%2FG063.mp4?alt=media&token=37a9751e-ca64-4291-9085-9f23279aed9a>" %}

## Understand who can open the link

A share link points to the existing conversation; it does not create a frozen copy or invite named recipients. The page loads the conversation's current saved messages when opened, so later messages can change what the link displays. Export a reviewed copy when you need a fixed record.

For a public interface, anyone who receives or is forwarded the link can load the shared transcript. **A password on the assistant does not make its conversation-share link password-protected.** Do not distribute a link to a transcript that requires recipient-specific access on that basis.

For an interface using organization SSO or **Require Authentication**, the message service also checks the signed-in conversation owner. Another person may receive **Failed to load conversation** even if they can use the assistant. Copying a link does not grant them conversation access.

The Share dialog has no per-link recipient list, expiry, or revoke control. Removing a link from an email or chat does not invalidate copies. If a link has reached an unintended audience, contact the project administrator to review access and conversation retention; do not assume an assistant password change revokes it.

## Review what you will share

Review the conversation and its attachments before sharing.

![Conversation content before sharing](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/fKIeG0c41hlT2l8JLlG4/assets/g063-g063-01-review.png)

Include only information intended for the recipients who will receive access.

## Create a share link

Open Share and inspect the conversation preview.

![Conversation share link controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/2REdOK5NzRS6zj5QuJEe/assets/g063-g063-02-preview.png)

Check the title and message contents before generating or copying its link.

Select Copy Share Link and use the generated address.

![Conversation share link controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/NGY15oywh3Qjz9TYbRSo/assets/g063-g063-03-copy.png)

Share it only with the intended audience rather than constructing a conversation URL yourself.

## Open the shared conversation

Open the shared link in a separate browser session using the intended recipient’s access. For a public or password-only interface, also test a signed-out session. Inspect the recipient view rather than relying on the owner’s already signed-in session.

![Shared conversation recipient view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/M8yNsk1OIByO7calsTY1/assets/g063-g063-04-viewer.png)

Confirm that it contains only the intended messages and inspect attachment names, image previews, citations, and links displayed with them. Check which actions, such as export, are available. Do not assume that an attachment is omitted because the view is read-only.

Compare the shared view with the original conversation.

![Shared conversation recipient view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/YtzJl4MrfGxAgdA5qegQ/assets/g063-g063-05-original.png)

The original may allow new messages and other actions that are not available in the shared view.

## If the recipient cannot open the conversation

Confirm that the link was copied from **Share** and that the conversation is still available. For authenticated interfaces, sign in through the original assistant first and retry; a different user may still be blocked by conversation ownership. If you need to deliver a fixed excerpt to another authorized person, review an export and share it through your organization's approved document-sharing channel. Exported copies have their own access and retention outside StackAI.

## Important behavior

The shared view can offer different controls from the original conversation. Review what recipients can see before distributing the link.

## Continue

* [Interface authentication and access](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md)
* [Use a published chat](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/use-a-published-chat.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/share-a-conversation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
