Knowledge

A public copy you cannot recall

You want to show someone a conversation, and you find Share conversation. It makes a read-only copy of the conversation as it stands at that moment, with its own web address. Anyone who has the address can read it without signing in. Once the copy exists, nothing in Lexika can take it down.

Who can share, and from where

Only the owner of the workspace a conversation lives in can share it. In a workspace you created, that is you. The owner can share any conversation there, including ones teammates started. Admins and members get no share icon or menu item, and /share shows them Owner only. If that is you, ask the owner to share the conversation.

The owner finds Share conversation in three places:

• The share icon near the far end of the chat header, opposite the sidebar button.
• The three-dot menu beside a conversation in the sidebar. On a wide screen it appears when you point at the row.
• The message box. Type /share and pick Share conversation.

Nobody can share while an answer is still being written. The header icon disappears, the sidebar row shows a moving progress animation in place of its three-dot menu, and /share shows Wait for the response.

Mini Apps conversations, such as a Council, cannot be shared. In them, /share shows Only in chat. In a workspace the owner has disabled, the dialog shows THIS_WORKSPACE_IS_DISABLED instead of a link.

What opening the dialog does

The Share conversation dialog starts making the link at once, showing Creating share link… while it works. Opening the dialog is enough to create the link, even if you close it without copying anything. Nobody can open that link unless you give them the address, which cannot be guessed.

The finished link sits in a read-only box, with an open-in-new-window icon button beside it (tooltip Open). A long link can be cut off in the box, and Copy link copies all of it. The shared page asks search engines not to list it.

A conversation with more than 1,000 messages, or about 5 MB of text, cannot be shared. The dialog shows CONVERSATION_SHARE_TOO_LARGE and a Retry button in place of the link, and retrying gives the same result.

What the link shows

The shared page puts the conversation's title at the top, with a line such as Shared conversation · 24 messages under it.

In the link

• Every question and answer, in order, with the time of each.
• The name of the model that wrote each answer.
• Comments, yours and your teammates', still marked as comments.

On the shared page, every question and comment looks as if the reader had sent it.

Left out

• Author names, yours included. No question or comment shows who wrote it. A name typed inside a message, such as a greeting or a signature, stays.
• Files and images, both the ones people attached and the ones the assistant made. A message that had any ends with the line [Attachment omitted from shared conversation], once, however many it had.
• The model's reasoning. Lexika does not save it with the answer, so no link can include it.
• The activity behind an answer, such as web searches, connected app calls and Brain saves.
• Reactions.

Leaving out a file does not leave out what was said about it. If an answer quotes a document, an email from a connected app or a note from a Brain, that text is in the link.

The link never updates

A link always shows the conversation exactly as it was when the link was made. Later messages, edits and regenerated answers never reach it, and a comment deleted afterwards stays in it.

To share a newer version, open Share conversation again. If nothing has changed, you get the same link back. If a message, a comment or the title has changed, Lexika makes a new link. A reaction, a pin or a move to another folder does not count as a change. The old link stays live and keeps showing the old version.

You cannot take a link back

Lexika has no way to stop sharing. Deleting the conversation does not remove the link, and neither does deleting its folder or the workspace. Lexika keeps no list of the links you have made. Anyone who has a link and a Lexika account can also keep their own copy.

Treat every link as permanent, and as public as the people you send it to. To show a conversation without leaving a public copy behind, choose Export in the conversation's three-dot menu in the sidebar and send the file instead.

What a viewer can do with it

A viewer can read the conversation but cannot reply, react or comment there. A bar at the bottom of the page reads Continue this conversation.

• Signed out. The bar offers Sign in, which brings the viewer back to the same page afterwards.
• Signed in. The bar offers Fork conversation. It opens a Fork into a workspace list, and picking a workspace creates the copy there and opens it. If the viewer picks a workspace other than the one they had open, a notice such as Forked into Design team confirms where the copy went.

The copy is an ordinary conversation in the chosen workspace:

• Its title is "Fork of" followed by the original title, cut to 100 characters. It sits at the top level, outside any folder.
• Every question and comment in it belongs to the person who forked it, including ones someone else wrote.
• It has no files. If the conversation depended on one, attach it again in the copy.
• Every message in it is dated at the moment of the fork.

Who else can read the copy is covered in the Knowledge Base article on who can read your conversations in a workspace.

If the address is wrong, for example mistyped or cut short, the page shows This conversation is unavailable. Deleting the conversation does not cause this, and a link that opened once keeps opening.

Before you share

• Read every question, answer and comment. Their text goes into the link as written, including any names typed in them.
• Check the title. It is the first thing a viewer sees, and it also names the browser tab. To change it, choose Rename in the conversation's three-dot menu in the sidebar.
• Share when the conversation is finished. Each share after a change leaves one more permanent copy behind.