Read and export the conversation archive
Who can read an organization's recorded conversations, how to search and filter them, what the archive never holds, and how to export it as JSONL.
When content logging is set to Full content, the organization keeps its own record of member conversations. This page is how that record is read, searched, and taken out.
The archive is empty unless someone turned content logging on. See Turn on content logging.
Who can read it
The owner, the security role, and auditors. Administrators cannot, and that is deliberate: the person who onboards staff should not be the person who can read what they wrote.
If your role does not include it, the page says so rather than showing you nothing.
Read it
- Open your organization in the dashboard and go to Conversations.
- Search what was written, or filter by the client it came from: chat, the CLI, the IDE, the API, or Slack.
- Open a conversation to read it as it happened.
Search here is a plain text lookup over the record, not a ranked search. It is built for finding a specific exchange during a review, which is what it is for.
What the archive holds
- What each member sent and what the model replied, in order.
- The client, the model, and the time.
- A mark on any message that was shortened to fit the record.
What it never holds: images, uploaded files, tool output, or instructions. It is a record of the conversation, not of the workspace around it.
Export it
Export writes the archive as JSONL, one assembled conversation per line. Two options decide what goes in:
- Include shortened messages, off by default.
- Include instruction turns, off by default.
The export panel describes the format as "the format fine-tuning pipelines read", and adds the line that matters: your data, for your own use. An organization can take this export and train on it. Dropstone does not. See Is your data used to train models?.
Reading it is recorded
Everything you do on this page is written to the organization's audit log, naming you, what you filtered on, and what you searched for. Members can see that their conversations are being recorded, and they can see that the record was read.
The audit log itself cannot be edited or deleted from, by anyone.
Related articles
- Turn on content loggingHow an owner turns on full content logging for an organization, what the confirmation means, how to tell members, and how to turn it off again.
- How an organization manages its dataThe three settings an owner controls for an organization, what each one stores, who can read it, and the limits of the strongest setting. Content logging, product telemetry, and retention, in one place.
- Is your data used to train models?On an organization account, never. On a personal account, only if you leave the setting on. What is collected, what is never collected, and what deletion can and cannot undo.
- Dropstone for teams and organizationsAn organization gives a company one Dropstone account structure, centralized billing, members and teams, shared memory, and enterprise sign-in. What an organization is, roles, and how to set one up.