Team

Team lets one person share their connected provider accounts with other people. Members call the shared accounts with their own API keys, and the owner decides who is in the team, which accounts are shared and how much each member may use.

You can own one team or belong to one team at a time. Owning a team counts as belonging to it.

What is on the page

The page changes with your role.

Without a team, the page lists the invitations waiting for your Google account, each with Accept and Decline. With none, it says so. New team in the header starts your own.

As the owner, the team name at the top opens a menu with Invite member, Refresh and Delete team. Below it:

• Members: everyone in the team and every pending invitation. Role is Owner, Member or Invited. Limits summarizes what each person may use; it reads No access when a member has no limit yet. Hover, focus or tap it to see each limit's usage, window and next reset. Edit on a member's row opens Limits and Remove; a pending invitation has Revoke.
• Shared accounts: the accounts the team may use, with their provider. Manage changes the list.

As a member, the team name menu holds Refresh and Leave team. Below it:

• Your limits: one row per limit the owner gave you, with Scope, Window, Usage and Next reset.
• Shared with you: the accounts the owner shared, marked with the owner's name.

Create a team

1. Open Team in the sidebar.
2. Choose New team.
3. Enter a Team name and choose Create team.

Invite a member

1. Open the team name menu and choose Invite member.
2. Enter their Email address and choose Create invite.

There is no link or code to send. The invitation appears on the Team page of whoever signs in with that Google account, and they choose Accept or Decline there. It expires after 30 days, and you can Revoke it from the members table before then. Someone who already belongs to a team has to leave it before they can accept yours.

Share accounts

1. In Shared accounts, choose Manage.
2. Tick the accounts the team may use, then choose Save.

Only accounts of the built-in providers can be shared: Claude Code, Codex, Grok and Antigravity. Custom endpoints and local models cannot. If you have none, connect one on Providers first.

Members never see the credentials of a shared account. They see its label, its status and the allowance you gave them. Unsharing an account also removes every limit scoped to it.

Give a member access

A limit is what grants access. A member without any limit cannot use anything the team shares, and a shared account that none of their limits covers stays out of their pool. Your own use of the accounts you share is not restricted until you add limits for yourself.

1. On the member's row, choose Edit, then Limits.
2. Choose Add limit.
3. Pick what the limit covers: Whole team, One provider, One account or One model of an account. For the last three, pick the provider, account or model next.
4. Under How much?, choose what it Counts: Requests, USD or Unlimited. For Requests and USD, set the Window (Day, Week, Month or Total) and the Ceiling; unless the window is Total, also the Time zone and Next reset.
5. Choose Add limit to put it on the member's list, then Save changes.

To give a member unrestricted use, add an Unlimited limit at the scope they should have. It has no ceiling and nothing to reset.

How limits combine:

• A request has to fit inside every limit that covers it. Overlapping limits are never summed.
• When one is used up, that account is skipped for that member and the request moves to the next account in their pool. If no account is left, the request fails the same way it would without a team.
• USD is the proxy's estimate from list prices, not a bill.
• Taiwan browsers default the time zone to UTC+8. Schedules use a fixed UTC offset and do not follow daylight saving time.

Edit or reset a limit

To change a limit:

1. Open the member's Limits and choose Edit on the row.
2. Change what it counts, its ceiling, window or next reset, then choose Apply changes.
3. Choose Save changes.

What happens to the usage already counted:

• A new ceiling keeps it.
• A new schedule keeps it until the first new reset, which the dialog shows before you save.
• Changing what the limit counts replaces the limit, so its usage starts from zero.
• The scope cannot be edited. Remove the limit and add a new one.

To start a limit over now, choose Reset usage on its row, then Reset now. Only that limit resets. Other limits, past records and the next scheduled reset stay as they were, and requests that began before the reset do not count against the new window. With unsaved edits pending, the button reads Save and reset: your edits are saved first.

Daily and weekly limits reset at the chosen time. Monthly limits reset on the chosen day, or on the last day of a shorter month without moving later months. Total never resets on its own.

What members see

Shared accounts appear on the member's own Providers page, under their provider, marked with the owner's name. Model ids do not change: a member calls claude-code/<model> with their own key, and the pool behind it holds their own accounts and the shared ones.

New shares sort below the member's own accounts. A member can move a shared account up or down, and that order is theirs alone. Instead of the owner's usage windows, a shared account shows the member their own used and ceiling, one bar per limit that covers it. Under an Unlimited limit there is no allowance to show, so they see the account's own limits, such as 5h and Week.

A team does not add requests to anyone's plan. Every request still counts against the sender's own allowance on Usage first; team limits are a second check on top of it.

Leave, remove or delete

• A member leaves: team name menu, Leave team.
• The owner removes a member: Edit on their row, Remove.
• The owner ends the team: team name menu, Delete team. The owner cannot leave otherwise.

When someone leaves or is removed, the shared accounts drop out of their pool on their next request and their limits go with them. Deleting the team removes every share and every limit. Nobody's own accounts, keys or logs are touched.

Related pages

• Providers: connect the accounts you want to share, and where members see shared accounts.
• Usage: each person's own plan allowance.
• How requests are routed: how the account pool picks the next account.