---
title: Notes team vaults
description: Give one of your organisation's teams a shared Notes vault, see who opens it (subteams included), close it when it is empty, and share notes with a team.
section: cloud
order: 121
audience: [user, agent, builder]
sources: [services/nodejs-cloud/lib/globe/teams.ts, services/nodejs-cloud/lib/globe/index.ts, services/nodejs-cloud/lib/globe/share.ts, services/nodejs-cloud/app/globe/api/teams, services/nodejs-cloud/components/globe/TeamSettings.tsx, services/nodejs-cloud/lib/globe/mcp/teams.ts, services/nodejs-cloud/migrations/0219_globe_vaults.sql, docs/adr/0075-globe-team-vaults.md, docs/adr/0077-org-teams.md]
features: [cloud.globe, cloud.migrations]
---

A Notes vault is personal (yours), the organisation's (everyone in the org reads it), or a team's. A team vault belongs
to one of your organisation's teams, the same teams Venom Tasks and the rest of Venom Cloud use
([Teams, subteams and roles](/docs/cloud/teams.md)). Its notes, databases and files are read and written by the team's members, and
nobody else in the org sees them unless that person is an org admin.

## Who opens a team vault

Membership flows down. If you are in a team, you are also in every subteam under it, with the same role. So:

- A member of **Engineering** opens the vaults of Engineering and of its subteam **Platform**.
- A member of **Platform** opens Platform's vault, not Engineering's.
- An **org admin** (`org:manage`) opens every team vault, member or not.
- Anyone else in the org gets 404 for the vault and its notes.

| Who | Read and write notes | Open or close the vault | Rename the team, change its people |
|---|---|---|---|
| A **member** of the team, or of a team above it | yes | no | in Settings → Teams, if they are a team admin |
| An **admin** of the team, or of a team above it | yes | yes | yes, in Settings → Teams |
| An **org admin** | yes, in every team vault | yes | yes |
| Anyone else in the org | no: 404 | no | no |

- A personal vault is never part of a team. An org admin opens every team vault, but never another member's personal
  vault.
- Changes in Settings → Teams take effect on the next request: adding someone to Engineering opens Platform's vault for
  them at once, and moving Platform out from under Engineering closes it for Engineering's members. A live editor that
  is already open keeps its connection until it reconnects.
- Someone who leaves the org opens nothing, even if they are still listed in a team.

## Start a team vault

Open the vault switcher at the top of the file list in Notes and pick **New team vault…**:

- **For a team:** pick one of your organisation's teams that has no vault yet. You can open a vault for a team you are an
  admin of (directly or through a team above it); org admins can open one for any team.
- **Or a new team:** type a name. Org admins can make a top-level team; a team's admin can make a subteam under it (pick
  **Under**). You become the new team's first admin and its vault opens.

A member who is not an admin of any team can't make a team here. Ask an org admin, or a team's admin, in
[Settings → Teams](/docs/cloud/teams.md#settings). A team or service key, one that belongs to no person, can't start a team vault.

## Vault settings

In Notes, **Settings → Team vault** shows which team the vault belongs to (for example `Engineering / Platform`), and who
opens it: the team's own people, then the people who come from teams above it, each with the team they come from. It is
read only. Rename the team, add or remove people, change roles, add subteams or leave in
[Settings → Teams](/docs/cloud/teams.md#settings), which the page links to.

### Close a team vault

**Settings → Team vault → Close team vault…** works only on an empty vault: no notes, nothing in its trash and no
databases. Move or delete the notes, empty the trash, then close it. The team and its people stay; you can open a vault
for it again later.

## What follows membership

Every Notes path that checks who is in a team uses the same rule:

- the vault switcher, the file tree, the graph, backlinks and the trash;
- search, Ask and related notes, in Notes and in the workspace's ⌘K;
- comments and their notifications, favourites, live editing and who is on a note;
- synced blocks and their copies;
- uploaded files (`/globe/api/files/…`);
- `venom globe sync`, the change feed and every MCP tool;
- **Mentioned in** on a Venom People contact ([Mention People contacts in Notes](/docs/cloud/globe-mentions.md)).

A team vault's notes are shared through the team. The **Share** menu on one says so: to give someone access, add them
to the team. Single-note invites, restricting and publishing stay on personal and org notes.

The Inbox, captured sources and the AI-chat import do not work in team vaults yet. Use your own vault or the org's
for those. The API answers `400 team_vault_unsupported`. The Memory folder, which mirrors approved org memory, lives in
the org vault.

## Share a note with a team

On a personal note, or an org note restricted to the people invited, **Share → Invite** offers your organisation's teams
as groups. A share to a team reaches the people in that team, including the members of the teams above it, the same
people who open that team's vault. It does not reach the members of the team's own subteams. A private team is offered
only to its members and org admins.

## API

The console session calls these. Errors use the usual JSON shape (`404 not_found` for a vault you do not open).

| Method and path | Body | Who |
|---|---|---|
| `GET /globe/api/teams` | | the team vaults you open (`teams`: your `role`, `null` for an org admin who is not a member, `canManage`, `members` counting people from parent teams, `notes`, `parentId`), plus `options`: the org's teams you can see, each with `hasVault`, `canOpen` and `canAddSubteam`, and `canCreateTopLevel` |
| `POST /globe/api/teams` | `{ "team": "<org team id>" }` | the team's admins, org admins; 201; `409 vault_exists` |
| `POST /globe/api/teams` | `{ "name": "Platform", "parentId"?: "<team id>", "description"?: "…", "members"?: ["ana@example.com"] }` | org admins (top level), the parent team's admins (subteam); 201, you are the admin; `409 team_exists` when a vault has that name |
| `PATCH /globe/api/teams/{id}` | `{ "name"?, "description"? }` | the team's admins, org admins; renames the org team |
| `DELETE /globe/api/teams/{id}` | | the team's admins, org admins; closes the vault; `409 team_not_empty` |
| `GET /globe/api/teams/{id}/members` | | anyone who opens it; each person with `role`, `inherited` and `via` |
| `POST /globe/api/teams/{id}/members` | `{ "email" \| "uid", "role"?: "member" \| "admin" }` | the team's admins, org admins; the same as adding them in Settings → Teams; `404 no_such_member`, `409 team_synced` |
| `PATCH /globe/api/teams/{id}/members/{uid}` | `{ "role" }` | the team's admins, org admins; `409 last_admin` |
| `DELETE /globe/api/teams/{id}/members/{uid}` | | the team's admins and org admins remove anyone; `me` leaves; someone in through a parent team answers 404 (change the parent team) |

Every note, tree, search, graph, database, file and export call takes the team's id as `vault`. `GET /globe/api/vaults`
lists team vaults between your own and the org's, each with `team: { role, canManage }`.

## Agents

On the workspace MCP and its REST twin:

| Tool | REST twin | Does |
|---|---|---|
| `globe_team_list` | `GET /api/v1/team-vaults` | the team vaults you open |
| `globe_team_create` | `POST /api/v1/team-vaults` | open a vault for an org team (`team`), or make a team and its vault (`name`, `parentId`); needs a personal key or a connected app |
| `globe_team_update` | `PATCH /api/v1/team-vaults/{team}` | rename the vault's team |
| `globe_team_delete` | `POST /api/v1/team-vaults/{team}/delete` | close an empty vault (the team stays) |
| `globe_team_member_list` | `GET /api/v1/team-vaults/{team}/members` | who opens it, parent teams included |
| `globe_team_member_add` | `POST /api/v1/team-vaults/{team}/members` | add someone to the team, or change their role |
| `globe_team_member_remove` | `POST /api/v1/team-vaults/{team}/members/remove` | take someone out of the team, or leave with `"me"` |

The member tools change the organisation team, exactly as `org_team_member_add` and `org_team_member_remove` do
([Teams, subteams and roles](/docs/cloud/teams.md)). `globe_vault_list` shows team vaults. Pass a team's id as `vault` to
`globe_note_write`, `globe_note_list`, `globe_note_search` and the database tools. A team or service key has no member,
so it sees no team vaults. See [Notes pages over MCP](/docs/cloud/globe-pages-mcp.md) for the rest of the tools.

```json
{"name": "globe_team_create", "arguments": {"team": "0196…"}}
```
