Team brain
The team brain is a shared Altretta vault whose note contents are end-to-end encrypted and whose access is cryptographically revocable — your team gets one trusted knowledge base, and nothing you sync through can read what's inside your notes.
Revoking someone is a cryptographic operation, not a permission toggle. Removing a member rotates the vault's data key and re-encrypts the store under the new one, so the person you removed cannot read anything they no longer hold a key for — whatever access they may still have to the underlying files.
What the team brain gives you
| Capability | Altretta |
|---|---|
| Native team collaboration | Yes |
| End-to-end encrypted note contents | Yes |
| Sync with no vendor server in the path | Yes — you choose the shared folder |
| Cryptographic per-member revocation | Yes — the data key is rotated and the vault re-encrypted |
| Signed, anti-rollback membership roster | Yes |
Filenames and folder structure are not encrypted in a team vault. Only note content is. Anyone who can read the shared folder still sees every note's path and filename, and the membership roster. If hiding names and structure matters to you, see The encryption model for exactly what is and isn't covered.
How it works, in one line each
- Note contents are encrypted before they leave your device, with a per-vault key wrapped individually for each member — but names and structure stay in the clear. See The encryption model.
- Four roles — Owner, Admin, Writer, and Reader — decide who can write and who can only read. Membership itself is managed by the Owner. See Roles & permissions.
- Access is a cryptographic fact, not a setting — invite someone and their copy of the key is created; revoke them and the key is rotated so their old copy opens nothing new. See Invite & revoke members.
- Sync runs through a shared folder you choose — iCloud, Dropbox, Syncthing, a network share, even a USB drive. There is no Altretta sync server. See Encrypted sync.
- Every member on the roster consumes a seat, whatever their role. See Plans, seats & Enterprise SSO.
Explore the team brain
The encryption model
Per-vault keys, per-member key wrapping, and exactly what stays readable.
Roles & permissions
Owner, Admin, Writer, Reader — and how the read-only lock actually works.
Invite & revoke members
Import a teammate's public identity, and revoke access by rotating the key.
Encrypted sync
Cross-device sync through a shared folder you choose, with no vendor server.
Plans, seats & Enterprise SSO
What the Team tier unlocks, how seats are counted, and Enterprise single sign-on.
New to the team brain? Read The encryption model first — it's the foundation everything else builds on.
Related
Encrypted sync
How a shared vault stays current across every member's devices.
Your signing key
The key that signs your changes and identifies you in a shared vault.
Verifiable knowledge
The signed history every member's edits are recorded in.
Glossary: team brain & seats
Quick definitions for team brain, seat, and Reader.