Skip to main content
API7.ai Logo

Teams

Teams group organization members for ownership, attribution, and shared governance. Budgets, rate limit policies, and MCP access can use the team identity to control traffic from team-bound caller API keys.

Team membership and caller API key binding serve different purposes. The roster identifies who belongs to the team. Traffic counts toward team controls only when the caller API key used for the request is explicitly bound to that team.

Create a Team​

  1. Open Teams and select New team.
  2. Enter a Display name and an optional Description.
  3. Select Create team.

The team appears with its member count and Team ID. Select the team name or Manage to open its detail page.

Copy the Team ID when another guide requires TEAM_ID. The same UUID appears at the end of the team detail page URL.

export TEAM_ID="YOUR_TEAM_ID"

Add and Manage Members​

Team members come from the organization member pool. Create or invite the member before adding them to a team.

  1. Open the team detail page.
  2. Under Members, select Add member.
  3. Select the Org member and assign the team role Member or Lead.
  4. Select Add member.

The Member and Lead labels belong to the team roster. They do not replace the member's organization role. When a team has one lead, promote another member before demoting or removing the only lead.

Use the role selector on a member row to change their team role. Select the remove action to remove the member from the team without removing their organization membership.

Bind Caller API Keys to the Team​

Team membership alone does not attribute traffic to the team. Bind each caller API key that should use team budgets, rate limits, or MCP access:

  1. Open the environment and select API keys.
  2. Create a key with New API key, or edit an existing key.
  3. Select the team in Team.
  4. Optionally select an Owner. After choosing a team, the owner list contains only members of that team.
  5. Create the key or save the changes.

The API key row shows its team binding. A member's personal key does not count toward a team merely because that member appears on the roster.

Configure Team Controls​

The team detail page provides Team budget (shared), Per-member budget, and MCP entitlement controls. Related guides cover the complete behavior:

  • Budgets explains shared team budgets and separate allowances for each member in a team.
  • Rate Limit Policies shows how to match a team and divide its quota into per-member buckets.
  • MCP Access Policies configures the MCP tools inherited by team-bound keys.

Use the dashboard to create, edit, delete, and manage membership for teams. The public AISIX Cloud Admin API supports team entitlements, but team lifecycle and membership operations are not currently part of its public contract.

Sync Teams from an Identity Provider​

SCIM directory sync represents an identity provider group as a team with the same name. Group membership changes update the team roster automatically. Manage the roster of a directory-synced team in the identity provider so later synchronization does not overwrite dashboard changes.

Directory-synced teams can use the same caller API key bindings, budgets, rate limit policies, and MCP entitlements as teams created in the dashboard.

Edit or Delete a Team​

Open the team detail page and select Edit to change its display name or description. Select Delete to remove the team and its roster. The people on that roster remain organization members.

Next Steps​

Continue with Caller API Keys to create team-bound credentials. Then configure Budgets, Rate Limit Policies, or MCP Access Policies for the team.