What's private and what's shared
Understand Personal, workspace Owner oversight, channel visibility, and the audience for documents and other outputs.
Working in a workspace means choosing an audience as well as a place to work. The person who starts a thread remains its owner, but workspace Owners can review workspace conversations. Library documents and Channels have their own sharing rules. Check those boundaries before bringing sensitive context into a shared workspace.
Your workspace is a shared place, not a private account
Workspace Owners can review other members' workspace threads read-only, including threads started without a named agent. Members and Editors do not gain that oversight merely by joining or maintaining an agent.
Personal and workspace knowledge
Personal
Personal holds your private work. Workspace membership does not silently move that knowledge into the workspace or let its Owners browse your personal library.
Workspace agent knowledge
A workspace-owned agent uses its workspace's knowledge and its own attachments according to its settings. It does not inherit the personal memories of whoever happens to start the run.
Shared personal agents
A personal agent shared in for run-only use stays under its author's control. Sharing the capability does not open the author's wider personal library or give the workspace permission to edit the agent.
If you deliberately attach or share personal material, review the destination and audience. Personal separation does not undo a sharing choice you make.
Who can read workspace threads
Your workspace's Threads page starts with your own threads. An Owner can also review other members' workspace threads. That includes a conversation started in the workspace without selecting a named agent; the workspace itself provides its scope.
| Person | Access through workspace membership |
|---|---|
| The person who started the thread | Their own conversation, while its required access remains valid |
| Workspace Owner | Read-only oversight of other members' workspace threads |
| Workspace Editor | Their own threads; editing agents does not grant cross-member oversight |
| Workspace Member | Their own threads; running agents does not grant cross-member oversight |
Other deliberate grants, such as sharing a thread, are separate from the role matrix. A shared personal agent also has its own author-oversight rules; it is not the same relationship as a workspace-owned agent.
Owner oversight is a human review surface. It does not automatically give an agent permission to read every conversation its Owner can inspect. Agent retrieval follows the run's own access and knowledge settings.
One workspace run, start to finish
A support rep asks Scout, a workspace-owned agent, to review an escalation. The rep starts in Support operations rather than Personal.
- Context: Scout draws on its workspace skills and memories according to its configuration. It does not absorb the rep's personal memories.
- Conversation: the thread remains attributed to the rep. A workspace Owner can review it read-only; an Editor cannot open it merely because they maintain Scout.
- Outputs: the report and table remain associated with the work that created them. A separate workspace-library document has a broader audience.
- Learning: Scout saves a new lesson with the agent or to the workspace library according to its configured destination. Use suggestions and review when a lesson needs checking before it becomes shared guidance.
Workspace memories explains how to keep a lesson with one agent or promote it for broader use.
Library documents and other outputs
The workspace's Library helps you find accessible material in that scope. It is not a promise that every item has the same audience.
Workspace-library documents
Every workspace member can read a workspace-library document. Owners and Editors can contribute and curate; only Owners can permanently delete it. An agent producing a document for the shared library creates that broader audience deliberately.
Thread outputs
Files and tables produced for a thread follow the access attached to that work. Appearing in a workspace-scoped list does not make them all shared library resources. Check the item's sharing controls and the thread's audience before assuming a teammate can open it.
When an agent moves from Personal into a workspace, its transfer review explains which conversations and knowledge will move. Linked documents have explicit choices, such as copying into the destination or leaving them behind. Review those choices before confirming: moving an agent can broaden access to work that was previously personal.
Leaving a workspace
Leaving or being removed ends membership-based access. It does not delete past work or automatically move workspace content into Personal. Workspace-scoped threads and resources can continue to require membership, even when you originally created them.
Before handing off responsibility, arrange another Owner and review automations that depend on your connected accounts. Workspace roles and workspace agents explain those separate responsibilities.