Teams & organizations

Personal vs. team vaults

Personal vaults belong to you. Team vaults belong to an organization: every member can use them, and access to each folder follows the member's role. Switch between your personal account and your organizations with the switcher at the top of the sidebar.

Team & Organization

Team & Organization in the sidebar is the home of your teams:

• From your personal account it lists every organization you belong to, with its plan, seats and team vaults. Click Switch to Team workspace to open one, or Create Team workspace to buy Team for a new team.
• Inside an organization it opens the Team workspace: the seat meter, members and pending invitations, the team vaults, and shortcuts to each vault's folder permissions and share links.

Buying Team

Team costs $60/month (or $599/year) and always belongs to an organization:

• You already run an organization: open it, go to Settings → Billing, and choose Team. Only owners and admins can buy it.
• You don't have one yet: choose Team from your personal billing page and name your team. The organization is created after the payment succeeds, and you land on its dashboard with a setup checklist. Abandoned checkouts never leave empty organizations behind.

One organization can have one active Team plan. Team tokens are pooled for the organization and never mix with your personal allowance.

Seats

Team includes 3 seats, and the owner counts as one, so you can invite two teammates. The seat meter on the Members page shows how many are used. Pending invitations hold a seat until they are accepted, revoked or expire.

Need more seats? Extra seats cost $20 per seat per month. They cannot be bought in checkout yet: contact us and we add them to your team.

Inviting teammates

Go to Settings → Members, enter an email address and pick a role:

The invitee receives an email and joins after signing in (or signing up) with the invited address.

When someone leaves the organization or is removed, the API tokens (MCP and extension) and share links they created for its vaults stop working. A token never acts with more rights than its creator currently has: if an admin becomes a member, their admin tokens are limited to what a member may read. The member who pays for the organization's Team plan can't leave or be removed until that plan is cancelled.

Leaving a team

Open the member list (Settings → Members, or the Team workspace), open the menu on your own row and choose Leave organization. You lose access to its team vaults; to come back, you need a new invitation. The only owner can't leave: make another member an owner first. The same applies before you delete your account while the organization still has members.

Deleting an organization

An owner deletes an organization under Settings → General with Delete organization, typing its name to confirm. Every team vault of the organization is deleted with it, including its files and history; members lose access, and an active subscription is cancelled first.

Moving a personal vault into a team

Open the vault, go to Settings → Move vault to a team / organization, pick the organization, type the vault's name and confirm. Vaults move only into a Team workspace: if none of your organizations has Team yet, upgrade one or create a Team workspace first. The vault then uses the team's plan and token pool, and members open it according to its folder permissions. You can also do it from the Team workspace with Move a personal vault here. Moving a vault back to a personal account isn't possible in the app.

Your personal connections don't move with the vault: your own AI key, your own storage connection (GitHub or S3) and the vault's API tokens are disconnected, so the team sets up its own.

Folder permissions

Open a team vault and go to the Folders & permissions tab: it lists every folder (subfolders indented) with a short description, its file count, the roles that can open it and the people who hold those roles. View as member shows exactly what members can open. Change several folders, then save them together with one Save. Click Folder permissions on a folder, or the small shield next to any folder in the Explorer file tree, and pick the roles allowed to read it; the owner is always on. Restrictions cascade: a subfolder is never more open than the folders above it, including subfolders created later by an agent or an import. Restricted folders show a highlighted shield in the tree.

Admins can only change folders they can open themselves, so an owner-only folder stays owner-only. Connecting external storage (GitHub or S3) is owner-only too, because the mirror contains every folder.

Folder roles apply everywhere: in the dashboard, in Vault Chat, through MCP tokens with that role, and in the generated routing maps, which only list the folders a reader is allowed to see.

Share links for freelancers

Team vaults can create share links: expiring access to a single folder for someone outside your organization. Create them in a folder's Folder permissions dialog, or for any folder you can open under Agents & MCP (you always pick the folder yourself). Opened in a browser, a link shows the shared folder's description and file names, and how to connect an agent. Subfolders restricted more tightly than the shared folder stay hidden from the link. Freelancers never see SOUL.md or any other folder, and every change they propose waits in Quarantine for your approval. Links stop working when they expire, and you can revoke them earlier at any time.

A share link acts for the person who created it. It stops working when its creator leaves the organization, is removed or suspended, or can no longer open the shared folder, and when an owner of the organization is suspended. Owners and admins see and revoke only the links on folders they can open themselves. A vault can have up to 50 active share links.