Teams
A team is a shared account. A research lab, a biotech group or a project team owns labs, chats, workspaces, runs, experiments, files, a publishing namespace and a credit pool together, instead of each person keeping their own copies.
Create a team
Open the account menu in the Studio sidebar and choose Create team. Give it a name and a namespace, which is the handle its releases are published under, such as smith-lab/cell-cycle@1.2.0. You become its Owner.
An Owner can instead give the team the namespace they already publish under. See Adopting your namespace.
Invite people
From Settings → Teams → your team → Members, invite by email and pick a role. The invitation link is valid for 14 days. Someone without an account signs up first and then accepts. Pending invitations can be resent or revoked from the same page.
Roles
| Role | Can |
|---|---|
| Viewer | Open and read everything the team owns, and pull its private packages |
| Member | Everything a Viewer can, plus create and edit labs, chat, start runs, and publish private releases. Cancel and delete what they made |
| Admin | Everything a Member can, plus make work public, fork or duplicate team work, manage Members and Viewers, and set member credit limits |
| Owner | Everything, including managing Admins, transferring ownership and deleting the team |
A team always has at least one Owner. Only Owners can make someone an Owner or transfer ownership.
Work in a team
The Working in switch at the top of the sidebar picks the account new work goes to. In a team, the lab, chat and run lists show the team’s work, and anything you create belongs to the team.
Each lab, chat and run shows its owner. Your permissions come from your role, and buttons you can’t use are hidden or say Ask a team admin.
To move a lab you own into a team, open its menu and choose Transfer to team. Owners and Admins can move a team lab back to a member. Published releases keep their exact references either way.
Chat together
Every Member can post in a team chat, one turn at a time. While someone’s turn is running, the composer shows whose turn it is. Each message shows who wrote it.
Approvals in a turn are answered by the person who started it, or by an Admin or Owner. Viewers can read the chat but can’t post.
Credits
Runs and cloud sessions on team labs and chats are paid from the team’s credit pool, not from the person who started them. Free work stays free: free-beta agent and API runs and Studio workspace runs never draw on the pool.
Admins and Owners manage the pool from Settings → Teams → your team → Billing. They can:
- buy credit packs for the team;
- set a monthly limit for each member;
- see the last 30 days of use by member.
When the pool or a member’s limit runs out, runs are refused with a message naming the team. Refunds go back to the pool.
Keys and agents
An API key or an agent connection can be made for a team instead of for you. It works only in that team: it sees and creates the team’s work, never your personal labs, and it can do no more than your role allows. See Connect your agent and Developer API quickstart.
Settings → Teams → your team → Integrations lists the keys and connections that work in the team. Admins and Owners see and can revoke everyone’s; others see their own.
Leaving
Leave from the team’s Members tab, or an Admin can remove you. You immediately lose access to everything the team owns, including what you made for it. Keys and agent connections you made for the team are revoked. Your personal work is untouched.
The last Owner can’t leave. Transfer ownership first, or delete the team.
Activity
The Activity tab lists membership changes, lab transfers, credit changes, namespace changes and key and agent connections. Every member can read it.
Next steps
- Team namespaces: publishing under the team’s name
- Visibility and sharing: who can see what
- Connect your agent: connecting an agent for a team