# What's private and what's shared

Source: https://www.hyperagent.com/docs/concepts/teams/whats-private

> For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL.

Who can see your runs and their outputs on a team, what a team agent can and can't reach, and where a document ends up when an agent makes one.

Working on a team raises a question personal work never does: when I run a shared agent, what of this is mine, and who else can see it? The answer comes down to one rule.

A team shares agents, skills, and reviewed context. It does not gather everyone's conversations into one place. Start a run and the thread and everything it produces belong to you, with one deliberate exception for the person accountable for the team.

## One run, start to finish [#one-run-start-to-finish]

Follow a single run and every rule shows up in order. A support rep on the Support operations team asks **Scout**, an agent the team owns, to work through a backlog of escalations.

**What Scout brings to the run.** The team's memories and skills, plus anything attached to Scout itself. Not the rep's personal memories: a team agent never reads the personal knowledge of whoever starts it, so nothing from their private work leaks into a shared agent's run.

**Where the conversation lives.** The thread belongs to the rep who started it. Their teammates, including Editors who can edit Scout's configuration, cannot open it.

**What Scout produces.** The summary, the table, the published page: all of it lands in the rep's thread and their Library, owned by them like any other work.

**What Scout learns.** A lesson from the run goes wherever Scout's save destination points, which on a team agent is the team's memories or Scout's own. That's the one thing designed to outlive the rep's thread, because a shared agent that learns only for one person isn't shared.

**Who else can look.** The team's Owner, and no one else. That grant is read-only, it covers agents the team owns, and it exists so the person accountable for the team can audit what the fleet is doing.

## What never crosses [#what-never-crosses]

Three boundaries hold no matter how the team is configured.

A team agent reads the team's memories and its own, never the personal memories of the member running it. Your private context stays out of shared work.

Members and Editors see only their own threads. Editing a shared agent does not come with the ability to read what other people did with it.

Sharing an agent with a team does not widen what it can reach. It uses the context already available to it, not everything its owner has.

## Who can open someone else's run [#who-can-open-someone-elses-run]

|                                                        | Can open another member's run                                                                                  |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------- |
| **The person who ran it**                              | Yes. The thread and its outputs are theirs.                                                                    |
| **Owner**                                              | Read-only, on agents the team owns, from the agent's Activity tab. Artifacts from those runs come with it.     |
| **Editor**                                             | No. Editors maintain the agent; they don't read other people's work with it.                                   |
| **Member**                                             | No.                                                                                                            |
| **The owner of a personal agent shared with the team** | Their own agent's runs only. An agent shared in rather than owned by the team stays outside the Owner's grant. |

Owner oversight is something a person does, not a capability any agent gets.
An agent searching past conversations is limited to its own threads, and that
search is switched off entirely for runs started from Slack, email, webhooks,
Telegram, and channels, and for teammates running an agent shared with them.

## Where a document ends up [#where-a-document-ends-up]

Documents follow the same rule as everything else, with one wrinkle worth knowing before you go looking for a setting that doesn't exist.

* **What you create is yours.** A document you make in the app is personal, whatever scope you give it.
* **What a run creates lives with the run.** It sits in the thread that made it, owned by whoever ran it.
* **What a team agent creates for the whole team is a team document.** When a run on a team agent creates a document meant to be broadly available, it lands in the team's shared documents, where every member can read it, Owners and Editors can curate it, and Owners can delete it.
* **Moving an agent into a team asks about its documents.** The move offers a choice for each linked document: copy it into the team, or leave it behind and drop the link.

Team documents come from a team agent's own work or from an agent move. If you
want teammates to have something you wrote, attach it to a team agent they run,
or ask the agent to produce the shared version.

## Keep something to yourself [#keep-something-to-yourself]

If a piece of work should stay entirely yours, run it on a personal agent rather than a team-owned one. Nothing about a team-owned agent's run is hidden from the team's Owner, and no setting changes that: the audit path is the point of it. Personal agents have no such grant, so their runs stay yours even when the agent is shared for others to run.

## FAQs [#faqs]

No. Members and Editors see only their own threads. The team's Owner can read runs on agents the team owns, read-only, from the agent's Activity tab. That is the only cross-member path.

Not on an agent the team owns. The oversight grant exists so someone is accountable for what shared agents do. When work should stay private, run it on a personal agent.

No. It reads the team's memories and its own. This holds regardless of who starts the run, which is what keeps your private context out of shared work.

Whoever started the run. The thread, the files, and the published pages are theirs, and they appear in their Library. The team maintains the agent, not a shared folder of everyone's results.

There's no direct control for it. A team document is created by a team agent's own work, or by copying a linked document into the team when an agent moves there. To get material in front of teammates, attach it to a team agent they run.

The threads and outputs you produced remain yours. Leaving ends your access to the team's agents, skills, and memories, which is an access change rather than a transfer of your work.