# Who can see a view

A view's audience is set on its **top-level** view. The top-level view is the one at the root of its sidebar tree. Everything nested under that view inherits the same audience and holds no access of its own.

A view can never be more private than the view it sits under. To give one view its own audience, move that view to the top level.

## Two audiences

- **Anyone in the organization** — the default for a new view.
- **Specific people** — the creator, plus the people and teams you name.

Narrowing to **Specific people** removes everyone else immediately. Naming a team covers the people in the team and in its sub-teams. Removing the last grant of a top-level view is refused.

## The lock and who can change access

A small lock after a view's title in the sidebar means the audience is not the whole organization. Hover the lock and the tooltip names the audience.

Editing a view's access is part of editing the view, which is the **Manage views** row in Settings → Roles. [Open in Teamhood](https://app.teamhood.com/go/settings/roles)

## It hides the view, not the items

Restricting a view restricts who can open the view, not the items inside it. Who may read items comes from [Roles and permissions](../roles-and-permissions/).

## Moving a view changes who sees it

- **Into a folder or under another view** — the view inherits the destination's audience and loses any audience of its own.
- **Out to the top level** — the view keeps the audience it was inheriting.
- **Between trees** — if the move would publish a restricted view to the whole organization, you are asked to confirm first.

Undo does not restore a lost audience.