Skip to main content
Cortex Chat is a per-account product. Your conversations, projects, plans and files belong to the account you signed in with and follow you across devices. There is no team, no workspace membership, and no shared conversation: another account cannot open a thread of yours, and there is no control that invites someone into one. This page is the honest version of that. It covers what “per account” means for each thing a chat produces, what the Share button in the transcript actually does today, what a link to a single message is and is not, and the three ways you can genuinely pass a Chat result to another person right now.

​
Who can see what

The last row is the one that matters in practice. Everything inside Cortex stays with your account; the moment something becomes a file, it is yours to send like any other document. The transcript header has a Share control, and it always lands on the same state: Sharing is not on this deployment. Conversation sharing is not available yet, and Cortex will not invent a link it cannot honour, so you will never be handed a URL that quietly fails for the person you sent it to.
Exporting a whole conversation as a document is not available from the app either. There is no menu item for it anywhere in Chat. To pass on a conversation’s contents, export a deck from it or copy the text you need.
A message does have a link, and it is worth understanding exactly what it is for. Open a message’s Message actions menu and choose Copy link to message. The dialog is titled Link to this message and tells you what the link does: Opens the conversation at this message for anyone with access to it. It adds the consequence: Anyone without access to this conversation will be asked to sign in. The field is labelled Message link, the link is marked Expires in 7 days, and copying it confirms with Link copied. Read that carefully and the limit is clear. The link grants nobody anything. It opens a conversation at a particular message for someone who could already open that conversation, and because Chat is per account, that someone is you. Treat it as a deep bookmark into your own thread, which is what makes it useful for a long research conversation you want to come back to at the right spot. Three more things you may meet in the same menu:

​
How to share a Chat result today

Three routes work, and all of them end with you sending something yourself.
1

Export a file and send it

From an answer, choose Export to build a deck from an editable outline; from the transcript header, Export as deck does the same for the whole thread. The file is saved to Library and can be downloaded. See Export documents.
2

Copy the answer

The answer’s action row has Copy, which becomes Copied on success and Copy failed if the clipboard write is refused. This is the fastest way to move a paragraph into an email or a ticket.
3

Download a table

When an answer contains a table, the Export as spreadsheet link under it downloads the rows as a comma-separated file immediately, with no dialog and no allowance spent.
A note saved from a selection, through Save to Library, is worth mentioning here because its own wording invites confusion: Saved in Chat Artifacts. Available from Chat, Code and Bot. That means the note is reachable from your other Cortex products, not by other people. It is cross-product, not cross-account.

​
Signed out versus signed in

You can use Chat without an account. What changes when you sign in is scope and durability, not who else can see your work. While you are signed out, the sidebar keeps a count of the free messages you have left. Anything that needs an account refuses with an entitlement message and a Sign in action rather than failing silently. See Accounts and sign-in and Plans and quotas.

​
Where collaboration does exist

Nothing in a conversation is shared, and that is deliberate: a thread carries whatever you happened to paste into it. The sharing surfaces Cortex does have live outside a conversation, and these are the pages that describe them: