Most doors open. A few rooms kept.

Every folder in an organisation’s vault is open to every member until an admin binds it. Binding is the exception, not the rule, so the handbook, the shared projects and the company notes stay where everyone can reach them — in the explorer, in search, and in every conversation with a team agent.

An admin binds a folder in one of two shapes. A team folder belongs to the teams named on it: members of those teams open and edit it, and nobody else sees that it exists. A folder kept by a team is one everyone can read but only that team changes — the brand guide, the pricing sheet, the policy everyone relies on.

To someone outside the team a team folder is absent, not locked — the same rule a fenced folder follows — and their conversations cannot reach it, not by asking nicely and not by running a routine. Admins are no exception. An admin who wants to see a team folder joins the team, which shows on the team’s people list like any other change.

To the team it is simply a folder, with a padlock and the team’s colour beside its name. Everything the team keeps there — notes, datasets, a dashboard built from them — stays inside. A dashboard shared with the whole company that draws on a team folder shows colleagues outside the team a plain note that the source is in a folder they cannot open, and nothing more.

Admins bind folders from the Teams tab: open a team, tap Bind a folder, and choose the shape. On the folder’s own page, Who can open this does the same for any folder.

At the top of the organisation’s vault sits My Vault, alongside the company’s own folders. Tap it once and a vault of your own appears, kept to you alone. Not even an admin can open it. Drafts, working notes, the proposal that is not ready — this is where they live while they are yours.

Publishing is a move. Ask your agent to move a file from My Vault into a shared or team folder and colleagues can see it; move it back and they cannot. Your team agents can work in there with you while you are in the conversation — a routine or a scheduled workflow never reaches it — and anything they remember from it stays with you rather than in the company’s shared memory.

It stays yours, and it stays yours after you leave. Nobody else in the organisation can open My Vault — not an admin, not the owner, and not once your membership ends. The owner’s whole-vault download leaves every member’s out, a former member’s included. Your own personal vault — the one a switch away from the company — is a separate place entirely and is never part of this.

Memory keeps to the room. A team folder stays searchable rather than remembered in full, so nothing from it surfaces in a colleague’s recall; the folder page says why. My Vault may be remembered in full — by you alone.

Syncs and uploads land where you may write. A folder you can read but not change is shown locked when you choose where a sync or a save should go, and a write into it is refused with the reason.

Sharing is still yours, exactly as with a fenced folder: the share sheet reminds you that sending a document to someone outside the organisation takes it outside the team.

When a team is deleted its folders stay closed rather than falling open, and the Teams tab lists them under Folders without a team until an admin gives them a new home or opens them to everyone.