Moving conversations
A conversation belongs to one place at a time: either your personal space or one workspace. You can move it from any place to any other, and the entire history (messages, tool calls, charts, files, memory references) moves with it.
The classic use cases:
- You started a conversation as a personal experiment, the analysis turned out to be useful, you want the team to see it → move to a workspace.
- You're cleaning up a workspace and a one-off exploration doesn't belong there → move back to personal.
- The team reorganised: a conversation sits in Sales but really belongs in Banking Workspace → move between workspaces.
Goal
You finish this page with a conversation moved to its right home, visible to the right people.
Prerequisites
- The conversation you want to move (you must be its owner or an admin of the source workspace).
- Edit-or-higher rights in the destination — you can't move a conversation into a workspace where you only have Viewer role.
Steps
1. Open the conversation
From your sidebar, click the conversation. The conversation header shows its current location (a workspace icon if it's in a workspace, none if it's personal).
2. Open the conversation menu
Click the ⋯ button next to the conversation title.
3. Choose Move to workspace…
The action lists every workspace you have edit-or-higher rights in, plus Personal if the conversation is currently in a workspace.
4. Pick the destination
Select the workspace (or Personal). The conversation moves immediately and the page reloads in the new context.
If the destination workspace's RAG context was previously empty for the conversation's referenced topics, the next chat turn may take a moment longer while it picks up the workspace files. After that, recall is normal.
What changes when you move
| Property | Personal → Workspace | Workspace → Personal | Workspace → Workspace |
|---|---|---|---|
| Visibility | Now visible to all workspace members | Now visible only to you | Now visible to new workspace members; lost from old one |
| RAG context | Workspace files become recallable | Workspace files no longer recallable | Different workspace's files become recallable |
| Memory entries | Workspace memory becomes recallable | Workspace memory no longer recallable | New workspace's memory takes over |
| Datasource binding | Unchanged | Unchanged | Unchanged |
| Share links | Still work — they don't depend on workspace | Still work | Still work |
| Conversation history | Unchanged | Unchanged | Unchanged |
The RBAC implication is the most important one: moving a conversation into a workspace gives every member read access to its history. Make sure the conversation doesn't reference data those members shouldn't see. Note that workspace members still need their own datasource grants to re-run queries — what they see is the cached output as you ran it.
Common issues
The destination doesn't appear in the move list. You don't have edit-or-higher rights there. Ask an admin of that workspace to upgrade you.
A teammate I expected to see the conversation can't. Either the conversation didn't actually move (refresh and check the workspace icon), or the teammate isn't a member of the destination yet. Both are easy to verify and fix.
Recall feels different after moving. The new workspace has a different RAG context. Old workspace's files are no longer searchable from the conversation; the new workspace's files are. If the conversation needs files from both, upload them to the destination workspace too.
Move action is missing from the menu. You're not the owner and not an admin of the source. Ask the owner.
See also
- Creating a workspace — destination has to exist first.
- Inviting members — control who sees the conversation after moving.
- Shared files and memory — what changes context-wise.