Team
Work with other people: share what you build, cap what the account spends, and keep a record of who changed what.
Open Team from the left sidebar (/user/team).
Working alone, nothing on this page applies to you. An account with no team behaves exactly as it always has.
Members and roles
Create a team, then invite by email. You get an invite link to pass on directly — useful when mail is slow or the person is sitting next to you.
| Role | Can |
|---|---|
| Owner | Everything. Cannot be demoted or removed — a team whose caps and membership nobody can change would be stuck |
| Admin | Everything except that: invite, change roles, set caps, edit anyone's work |
| Member | Build and run. Edit their own work; run a teammate's shared work |
| Viewer | Read only. Cannot run anything, because a run spends the team's credits and can send email on the company's behalf |
Each person belongs to one team.
Sharing
Sharing is per item and off by default, including for everything you created before joining a team. Nothing you wrote while your account was private becomes visible to colleagues because a feature shipped.
Work created inside a team starts shared, since a team that has to remember a toggle for everything shares nothing.
Automations, workflows, skills and Brain documents each carry their own switch. A shared item shows who it came from, and a teammate's item shows no edit or delete controls unless you are an admin.
Only the owner of an item can share or unshare it — not even an admin. Editing somebody's work and publishing it to their colleagues are different acts.
Shared Brain documents are searchable by the whole team, so a shared handbook answers everyone's questions. Private ones stay private, in chat and in search alike.
Limits
Monthly credits caps what the whole team can spend. At the cap, runs stop and say why rather than failing mysteriously.
Runs at once caps how many automations and workflows can be in flight across everyone. Useful when one person's busy watcher would otherwise starve everybody else.
Zero means no limit. Both are counted from what is genuinely happening — in-flight runs, billable runs — rather than a stored counter, which drifts the first time a worker dies mid-run.
Activity
Every meaningful action is recorded: team created, member invited, role changed, member removed, item shared, limits updated. Each line carries who did it and when.
This is a record, not a feed. It is there for the question "who turned that off?".
What a team is not
A team does not own anything. Automations, workflows, skills and documents stay owned by whoever made them; the team decides who else may see and run them.
That is deliberate. Transferring ownership of everything to a team would mean rewriting every query in the product, and every one of those is a chance to leak something.