A team workspace lets one account share its Team plan and its credits with other accounts. Members keep their own files and templates; what they share is the plan's limits and the owner's credits. Membership actions live in Profile → Team Workspace.
What a team is
A team is a workspace owned by a single account. There is no separate "create a team" button: a team is created when an account subscribes to a Team plan (Growth, Scale, or Enterprise) on the Pricing page. That account becomes the team's owner, and the team is named after it automatically.
A team shares two things with its members:
- The owner's plan limits. A member is limited by the team owner's plan, not by any personal plan; see Limits & Specs for the batch-size and concurrency numbers.
- The owner's credits. The team pool is the owner's balance made available to the members. See How team credits work.
A team does not share files, batches, or templates. Anything an account uploads stays in that account's own Files list and is not visible to the rest of the team; a batch belongs to the account that created it. Templates are also per account. For how a batch is created and what it holds, see Batches. What the team shares is capacity and credits, not content.
An account belongs to one team at a time. A member can leave and join a different team; an owner cannot join another team, because owning a team and belonging to one are the same slot.
| Team plan | Members the team can hold |
|---|---|
| Growth | 5 |
| Scale | 15 |
| Enterprise | 50 |
The owner counts toward this capacity. If you were already a member of a team and then subscribe to a Team plan yourself, the Pricing page warns you that buying it removes you from your current team and makes you the owner of a new one. See Plans & Credits for what each plan includes.
Inviting members
Only the owner can invite. There is no invite link — the owner generates a short invite code and shares it with the people they want on the team.
- Go to Profile → Team Workspace. As the owner you see the team name, a Capacity: current / maximum tag, and the member list.
- Click Invite Code. A six-character code (capital letters and digits) appears, with Expires in 30 minutes under it.
- Click Copy Code and send it to the person you want to invite.
A code stays valid until it expires or the team fills up, so it can be used by more than one person within that window. Clicking Invite Code again issues a new code and replaces the previous one.
Joining a team
Anyone with a valid code can join — the account does not need a paid plan of its own. In Profile → Team Workspace, an account that is not in a team sees a field labelled Enter 6-character Invite Code and a Join Team button.
- Enter the code the owner gave you.
- Click Join Team.
- The page reloads and the Team Workspace section changes to the member view, which shows the team name, the owner, the owner's plan, and Shared Credits Available.
A join is rejected if the code is invalid or has expired, if the team is already at its member capacity, or if the account already owns a team. To move from one team to another, leave the current team first, then join the new one with its code.
Leaving, removing, and disbanding
All three actions remove an account from the team and end its access to the team's plan and credits. None of them deletes or moves any files, batches, or results — those stay with the account that uploaded them.
Leaving a team
A member sees a Leave Team button in the Team Workspace section. Clicking it asks for confirmation and warns that you will lose access to team credits. After leaving, the account is back on its own plan and its own credits; the credits and files it already owns are untouched.
An owner cannot leave their own team. The owner's only way out is to disband the team.
Removing a member
The owner can remove a member from the member list: each row that is not the owner has a Remove action, which asks for confirmation before removing that account. The effect on the member is the same as leaving — they are out of the team immediately and lose access to the team's credits and plan.
Disbanding a team
Only the owner can disband. The Disband Team button asks for confirmation and states that all members will be removed and the action cannot be undone. Disbanding deletes the team: every member, including the owner, is released from it and the shared pool ends.
A team with an active Team subscription cannot be disbanded. The owner must cancel the subscription first; until then, disbanding returns a message telling them to cancel first. Cancelling the subscription does not by itself disband the team.
How team credits work
The team pool is not a separate wallet that the owner tops up. It is the owner's own credit balance, made available to the members while the team is active. That is why a member's Shared Credits Available is simply the owner's balance, and why the owner's account is the one charged when a member runs a batch.
When a member starts processing, the app checks the combined total — the member's own credits plus the owner's — before letting the run start. The charge is then drawn in this order:
- The owner's Plan credits.
- The owner's Lifetime credits.
- The member's own Plan credits.
- The member's own Lifetime credits.
In other words, the team pool is used before your personal credits. (The labels Plan and Lifetime are the two balances shown in the Credits tooltip in your profile.) Because the owner is charged first, an owner can see the runs a member made in the Credits Usage history, listed with the member's name.
The sharing is one-directional. The owner's credits can pay for a member's processing, but a member's personal credits are never used to pay for the owner or for another member. A member's personal credits are their own and stay with them through joining, leaving, or being removed. Leaving or being removed ends access to the owner's credits; it does not move or refund anything.
If the owner's Team plan is no longer active — for example the subscription lapsed or was cancelled — the team goes into a frozen state. A member sees a Frozen tag with a short explanation that shared credits and concurrency are suspended, the shared balance shows as zero, and the member can only spend their own credits until the owner's plan is active again. The team is not automatically disbanded by a lapsed subscription.
Credits charged for a run, and any refund when a run is cancelled or fails, follow the Model Tier recorded when processing started. See Model Tier.
Common questions
Can I be in more than one team at once?
No. An account is in one team at a time. A member can switch teams by leaving the current one and joining another; an account that owns a team cannot join a different team.
Do team members see each other's files?
No. Files and results belong to the account that uploaded them. Being on a team shares credits and plan limits, not the Files list or its contents.
Do team members share templates?
No. Templates stay with each account. Team sharing covers the plan's limits and the owner's credits only.
Can the owner leave or hand over the team?
No. The owner cannot leave the team, and there is no ownership transfer. The owner ends the team with Disband Team, which releases every member including the owner.
What happens to my own credits if I leave or am removed?
Nothing. Your personal credits stay on your account, whichever team you are in. You only lose access to the owner's shared credits and the team plan's limits.
What happens to the pool when the owner disbands?
The team and its shared pool end, and every member is released. The owner keeps the credits that were theirs; nothing is transferred to members. A member's own credits are unaffected.