Teams and billing
Manage a team
Invite teammates, manage seats and roles, and understand the difference between team access and task sharing.
Every Adam account starts with a personal team. A shared team lets people work together with shared integrations, tasks, and files. Model usage follows the plan seat assigned to each member.
If you belong to more than one team, use the team switcher to choose where you want to work.
Open team settings
Select your account menu, choose Settings, then open Team. The Team tab appears when you are in a shared team.
From Team settings, owners and admins can update the team, review seats, invite people, and manage members.
Team roles
| Role | What they can do |
|---|---|
| Owner | Manage the team, members, seats, and billing. |
| Admin | Help manage members, seats, and billing. |
| Member | Use the team's tasks, files, and integrations. |
Only grant Owner or Admin to people who should manage team access and billing.
Invite people and manage seats
Review available seats
Open Settings → Team and check the current seat count before inviting someone.
Send an invitation
Enter the person's email address and choose the appropriate team role.
Track the invitation
Pending invitations appear in Team settings. Invitations count toward seat capacity, so revoke an obsolete invite before reusing its seat.
Review access after joining
Confirm the member's role and remove connections or task shares they no longer need.
Team plans are billed per seat. Each assigned paid seat has its own monthly usage allowance, so adding a seat gives the assigned member their own included usage. Add-on funds remain shared across the workspace. See Billing and usage.
Control API and MCP access
In a shared workspace, owners and admins can open Admin > API & MCP to manage external access:
- Allow API and MCP access controls whether members can create API keys and connect clients. Turning it off also stops existing credentials from accessing the workspace without deleting them.
- Permissions members can grant controls the read and write scopes available to new and existing connections.
- Allow full harness execution controls
tools:execute, which permits direct commands and billable tools using workspace files, connected accounts, paired devices, and stored credentials. - The API key and connected-app lists let administrators review and revoke members' credentials.
Members can review their own connections under Settings > Developer > Connected apps. See MCP permissions for the difference between resource access and direct execution. Reconnecting a client does not override a workspace restriction.
Leave, delete, or remove access
Members can leave a team from Team settings. An owner can permanently delete an additional team from the danger zone after typing its name to confirm. Deleting a team cancels its active subscription and removes its tasks, files, invitations, and member access.
Your account's default team cannot be deleted separately because it holds your account-level workspace history. It is removed when you delete your account. Contact hello@adam.new if ownership of a team must change.
Before removing a member, review any tasks, published links, scheduled work, or integrations they manage.
Share one task instead
If someone only needs access to a particular result, use task sharing instead of adding them to the whole team. Invite them with Can view or Can edit, or publish a read-only link. Learn more in Work with tasks.