Conversation privacy
Who can read your Genius conversations in an organization: workspace visibility, what every role reaches, why only the owner can continue a chat, and the access log.
Inside an organization, Genius history is shared but writing is not. You can read your teammates' conversations in the workspaces you have access to — which makes it easy to pick up context on a project — but only the person who started a chat can continue it.
Where a conversation lives
Every conversation is stamped with the organization and the workspace that were active when you started it. That stamp never changes, and it's what decides who sees the conversation later.
This matters in practice: if you start a chat in the Production workspace and later switch to Experiments, that chat stays with Production.
What history you see
| Where you are | What the history shows |
|---|---|
| Personal space (no organization) | Only your own conversations |
| An organization, no workspace selected | Everything in the workspaces you can reach — this is the default, All Workspaces |
| An organization, a workspace selected | Only that workspace |
All Workspaces is the default view, so if a conversation seems to be missing, check whether you have a specific workspace selected in the switcher.
Which workspaces each role reaches
Workspaces have three visibility levels, set when you create them:
- All members — everyone in the organization. This is the default for new workspaces.
- Team only — the teams you authorize, plus anyone you invite individually.
- Private — only the people you invite.
What each role reaches:
| Role | Workspaces |
|---|---|
| Owner | All of them, including private ones |
| Admin | All of them, including private ones |
| Member | All members workspaces, those where they were invited, and team only ones belonging to their teams |
Owners and admins reach every workspace on purpose — it's what makes offboarding, audits and compliance possible. A private workspace hides a conversation from members, not from whoever administers the organization. If you need something no administrator can read, use your personal space.
What you can and can't do
| Action | Your conversation | A teammate's, in a workspace you reach |
|---|---|---|
| See it in the history | Yes | Yes |
| Open and read it | Yes | Yes — and it's recorded |
| Continue the chat | Yes | No |
| Cancel a running response | Yes | No |
| Rename | Yes | No |
| Delete | Yes | No |
| Rate a response | Yes | No |
Conversations in workspaces you don't reach simply don't appear, and they can't be opened by link either.
Reading a teammate's chat
When you open a conversation that isn't yours, the message box is replaced by a note telling you whose it is:
This conversation belongs to Ana Ruiz. You can read it, but only its owner can continue it.
This works the same on the web, desktop, iOS and Android. To carry on from something a teammate started, copy what you need into a new chat of your own — that also keeps credit usage attributed to the right person.
Access log
Opening your own conversations leaves no trace. Opening someone else's writes an entry to the organization's activity log, in Organization settings → Activity Log, under the Conversations filter.
Each entry records who opened it, whose it was, the workspace and its visibility, the role of whoever opened it, the IP address and the time. Entries where the workspace was private or team only are highlighted — those are the accesses an audit usually wants to find first.
The log is a record, not a restriction: it doesn't block anything, it leaves evidence.
Related
- Organizations & workspaces — roles, permissions and how to create workspaces
- Using Genius — what the assistant can do