# Teams

Members, roles, invitations, and what is shared across a team.


Every account belongs to exactly one team. API keys and their spend are attributed to the member who created them. Invite colleagues from the [members page](/members) when you want them on the same credits and rate card.

## Roles

- A team admin manages invitations, removals, suspensions, the team's name, and [billing](/docs/billing). A team always keeps at least one active admin.
- A member creates keys, sends requests, and sees the team's usage.

Everyone in a team sees the same [usage page](/usage): spend by model, the daily chart, and the request log, with each request attributed to its member.

## Invitations

Admins invite by email from the [members page](/members). A team holds up to five members, counting pending invitations. The invitee accepts, signs in, and immediately gets a personal key billed to the existing team. There is no second trial grant and nothing to wait for.

## What is shared, what is not

The credit balance, the rate card, and the throughput cap are shared. Every key in the team draws on the same tokens-per-minute budget; see [Rate Limits](/docs/rate-limits).

API keys belong to one member. Each member creates and revokes their own, and the request log says which member's key served each request.

## Removing a member

An admin can remove a member from the [members page](/members). Their API keys stop working straight away, and the usage they already ran stays on the team's bill. A removed member who signs in again gets a team of their own. A team always keeps at least one active admin, and a suspended member can't be removed; contact support instead.

## Suspension

An admin can suspend a member. The gateway stops accepting that member's API keys and keeps their usage history.