# Who can see what

> Who can see and change what in Whorl: the Space boundary, roles, what owners and admins cannot open, and how agents use one person's access.

Source: https://docs.whorl.work/access

Whorl has a small set of access rules, and they are the same in the web app and for agents.

## The Space is the boundary

Everything in a Space belongs to the Space: its Threads, Captains, Notes, Automations and Files. Whoever is in the Space sees all of it, and nothing inside is shared more narrowly. If something should be private to a few people, put it in a Space with only those people. See [Spaces](/spaces).

- **Company**: every current member of the company.
- **Personal**: only you, permanently.
- **Shared**: its own members.

## Seeing a Thread means working in it

There is no way to share a single Thread with one person. Everyone who can open a Thread can send it messages and steer it. A Thread never moves to another Space.

## Only a Thread's owner archives or deletes it

A Thread's owner is the person who started it. For a child Thread, it is the owner of its parent. For a Thread an Automation starts, it is the person the Automation runs as. For a Captain's Crew Threads, it is the person who created the Captain.

Space owners and company owners and admins cannot archive, restore or delete someone else's Thread. Anyone who can open a Thread can rename it.

## Administration is not visibility

Company owners and admins manage the company: its people, roles and agent setup. They cannot open a Space they are not in, or anyone's Personal Space.

| Role           | Can                                             |
| -------------- | ----------------------------------------------- |
| Company owner  | Manage people, roles and every company setting. |
| Company admin  | Add people and change agent setup.              |
| Company member | Work in the company and its Spaces.             |
| Space owner    | Archive and delete the Space.                   |
| Space admin    | Add people and change the Space's settings.     |
| Space member   | Work in the Space.                              |

See [Members and invitations](/members).

## Agents act for one person

A run of an agent acts for the person who sent the message or started it, with exactly that person's rights and their personal setup. Steering someone else's Thread never uses your keys, and your steering never uses theirs.

- A child Thread acts as the same person as its parent.
- A Captain in a Company or Shared Space uses the Space's content and tools, never anyone's personal tools. It asks before it writes, unless someone gave it standing consent.
- A Captain in a Personal Space is the exception: it has one person to act for, so it has every tool its owner has.
- An Automation runs as one person, the one who last saved its prompt, trigger or target. See [Automations](/automations).

## Access is live

Leaving a Space or the company ends access at once, including Automations that were running. Archiving a Space stops its Automations and Captains.

## Related

- [Spaces](/spaces)
- [Members and invitations](/members)
- [Agents and setup](/agents/setup)