Skip to main content
A squad groups organization members under shared settings. A member belongs to at most one squad. Organization-enforced settings still take precedence.
Squads table with Platform usage and unassigned members.

Local demonstration with fictional members and illustrative usage data.

Create and populate a squad

As an administrator:
  1. Open Team → Squads and click Create a squad.
  2. Enter its name, such as Platform, and create it.
  3. In Unassigned members, select members and use the squad row’s assignment action, or drag members onto the squad row.
  4. Check the squad’s member count and membership after the change.
Removing someone from a squad does not revoke their seat or remove them from the organization.

Configure the squad

Open the squad’s settings from its row. Save the section you change. Inherit delegates a choice; an explicit organization On, Off, or routing configuration can override the squad. See Gateway inheritance.

Choose how to control spending

For a hard limit, edit Spending limit in the squad table and choose its amount and period. Zero means no squad limit. Other applicable limits can still block a request. For staged routing, assign a Strategy, choose a shared or per-member budget, and decide whether to block at 100%. A strategy and a hard usage limit cannot coexist on the same scope. A budget monitor notifies someone about a configured usage limit. A routing budget is a different setting; do not assume a percentage monitor observes it.

Verify and maintain

Have a squad member send a new request. Inspect the model, provider, and compression result in Logs, then review the squad’s cost and token totals for the same period. When moving a member between squads, check their new effective settings and plugin assignments.