Team banks
A team bank is one memory bank several people share. Everyone in it can read it, assistants you point at it write to it, and the things you tell your own assistant stay yours.
What a bank is
Every account has a personal bank. It is what your assistants read and write by default, and nobody else can see it.
A team bank has members instead of an owner. It is the right place for what the team needs rather than what you need: which database the billing service uses, who owns which customer, why the schema is the shape it is. Memories in it belong to the bank, so they survive people joining and leaving.
Making one
- Open Banks and create a team bank.
- Invite people by email. Anybody who already has an account gets access straight away; anybody who does not joins automatically when they sign up with that address.
- Point an assistant at it — either an API key created with that bank selected, or an app you approve and choose the bank for.
Roles
| Role | Can |
|---|---|
| Owner | Everything a member can, plus invite people, change roles, remove people, rename and delete the bank |
| Member | Read the bank, search it, and save to it |
| Reader | Read the bank and search it — and nothing more. No assistant they connect can save to it |
Read-only membership is for the contractor, the auditor, the new starter: somebody who should see what the team knows without adding to it. Their assistants still search the bank; the bank simply is not offered as somewhere to save, and a save is refused if one is attempted anyway.
The last owner cannot leave or step down without either promoting somebody else or deleting the bank.
Where an assistant saves
This is a choice a person makes once, when connecting the assistant — never something the assistant decides per memory. The two tools stay two tools, and no model is ever asked to pick a bank.
| A connection that saves to | Can search |
|---|---|
| Your personal bank (the default) | Your personal bank and every team you are in |
| A team bank | That team and your other teams — never a personal bank |
Nothing personal can reach a team by accident. The obvious risk is a connection pointed at the wrong bank. The subtler one is an assistant reading something private and then writing a rephrased version of it somewhere shared — and no setting or instruction reliably stops that.
So an assistant that can write to a team bank cannot read your personal one at all. There is no path from a private memory to a shared one, because nothing can see both at once.
In practice that means your own Claude keeps writing to your personal bank while reading the team's, and a shared assistant — a CI bot, a team project, a second connector you add deliberately — writes to the team.
What stays separate
- Duplicates and replacements never cross a bank. The same sentence can exist in your personal bank and in a team bank; neither knows about the other. A fact saved to the team can never retire one of yours.
- Every team memory records who wrote it, and the team page shows what has happened in the bank — who saved and searched what, through which assistant.
- Leaving is immediate. Remove somebody, or leave yourself, and access ends that second. What was written stays: it belongs to the bank.
- So is a change of role. Make somebody a reader and their existing connections keep reading that bank and stop being able to write to it. They are not quietly repointed somewhere else.
Limits
Each bank has its own storage allowance — 5,000 memories by default — so a team bank does not eat into anybody's personal one. Daily operations are still counted per person, because they are what costs an embedding call.