Team
One plan for the whole team. Members get the team's access, and admins manage its keys.
A team shares one plan across as many seats as it buys. You become its owner, and you can invite people by email and give each one a role.
| Member | Role | Joined |
|---|
| Role | Expires |
|---|
Roles: a viewer sees everything the team's plan includes. An analyst can also export, save work and run jobs. An admin can also manage members, keys and webhooks, and read the audit log. The owner also manages billing and branding.
···
Applies to every team key and service account, in addition to each key's own list. Leave it empty to allow any address.
Shown on the exports and embedded components your team publishes.
A team key uses the team's plan, and any admin can manage it. A service account is a key that belongs to a system rather than a person: name it for the system that uses it, rotate it with a grace period, and it keeps working when staff change.
| Key | Kind | Scopes | Allowlist | Limit per minute | State |
|---|