Skip to main content

​
Teams

Teams is for groups that want to share one workspace and one bill while every person keeps their own usage allowance and API keys. Teams start at 2 seats, are billed monthly by card, and you can mix Team and Team Pro seats. For more than 200 seats, custom terms or invoicing, contact sales.

​
How it works

  1. Open Team in your dashboard and create a team.
  2. Buy seats from the Billing tab.
  3. Invite teammates by email, give each a role, and assign them a seat.
  4. Each member creates their own team API keys and points their tools at Openference as usual.
A seat’s allowance and keys are separate from the member’s personal plan and keys. Team keys use the same base URL and models as everything else (see Base URL & Authentication).

​
Roles

Only an owner can promote another member to owner (by transferring ownership).

​
Seats and billing

  • Adding seats is charged pro rata immediately.
  • Removing seats is allowed once the seat is unassigned; the unused time is credited on your next invoice.
  • Removing a member or unassigning a seat revokes that seat’s team API keys immediately.
  • If a subscription lapses, team keys stop working until it is renewed. Members’ personal accounts are not affected.
  • Each seat is capped at 100 requests per minute. Custom Enterprise agreements can set different limits.
Owners and billing admins can update the payment method and download invoices from the Billing tab.

​
Team controls

  • Allowed models — limit every member to an approved set of models.
  • Zero data retention — require that team requests only use providers classified as zero data retention.
  • Network allowlist — restrict team API keys to specific IP addresses or IPv4 ranges. Leave it empty to allow any network.
  • Single sign-on — team owners can require sign-in through their identity provider (Okta, Microsoft Entra ID, Google Workspace or any OpenID Connect provider). See Single sign-on and provisioning.
  • Audit log — administrative actions (invites, role and seat changes, key creation and revocation, policy changes, single sign-on changes) with who and when. Admins can export it as JSON or CSV.
Usage analytics for admins are metadata only: request counts, tokens and models. Prompt content is never shown to admins.

​
Allowance

Each seat has its own allowance with the same 5-hour, weekly and monthly windows described in Plans & Usage. Members see their own percentages on the team Overview; admins see each member’s percentages on the Members tab. When a seat’s allowance is used up, that seat waits for its window to reset or the team can upgrade seats.

​
Security

See the security overview for the controls available today and what is still in progress.