Teams - TunePlane

A team is a department, not a tenant. It is the unit capacity is budgeted to, at /admin/teams. Administrators only, and part of the commercial edition. A deployment where one team uses the platform needs none of this.

What you see

Region	What it shows
Team key	Lower-case letters, digits, `-` and `_`, up to 64 characters. It appears in URLs and on bills, and cannot be changed
Display name	What people read
Parent team	Teams nest. Top level is the default
Members	Who is in it, as Owner, Member or Viewer
Projects	Which projects this team owns, which is what decides whose capacity a run spends
Team quota	Concurrent GPUs, concurrent jobs, GPU-hours per day

With SSO group mapping configured, members arrive on their next sign-in rather than being added by hand.

A run’s budget comes from its project

Never from whoever submitted it. A person can be in several teams, and only the project answers whose capacity a run was. The team is stamped on the job at submit, so moving a project between teams later does not rewrite work already done.

Two quota semantics that invert

	Per-user quota	Team quota
Not configured	A limit of zero	No limit. Creating a team must not become a way to block everyone in it
An administrator	Exempt in some checks	Not exempt. Skipping a team’s budget spends another department’s money

Both quotas apply together. Either one over the line queues the job.

What you can do

Action	Effect
New team	Pick the key carefully; it is permanent
Add or remove a member	Or let SSO group mapping do it
Assign a project	`PUT /api/teams/project`, or from the project
Set the quota	`PUT /api/teams/{key}/quota`
Read its usage	`GET /api/teams/{key}/usage`

Next

Setting up teams and quotas · Working in a team · Billing · Approvals