Team configuration

A Team is the top-level container that owns members, schedules, and webhooks. Create a Team before any other resource.

Fields

Field	Type	Required	Default	Notes
`name`	string	Yes	—	Team name. Cannot be empty.
`description`	string	No	`""`	Free-text description. Up to 500 characters.
`members`	array	Yes	—	At least one member is required. Each entry is `{ user_id, role }` or `{ user_email, role }`.
`disabled_mcp_connections`	array	No	`[]`	IDs of MCP connections to disable for this Team. IDs must be positive; duplicates are removed; up to 100 entries.
`mcp_tool_overrides`	object	No	—	Per-tool authorization-layer overrides for MCP connections (restrict-only: a Team can tighten the inherited layer but cannot loosen it). Shape: `{ "<connection-id>": { "<tool-name>": "l1_auto" \| "l2_approval" \| "l3_hidden" } }`. Up to 1000 connection×tool pairs in total. The field is omitted from API responses when no override is configured.
`investigation_hints`	string	No	—	Optional free-text hints shown to responders to guide investigation.

Members

Each member entry identifies a user and assigns a role:

Identify the user by user_id or user_email. When both are given, user_email takes precedence.
role is one of team_admin or team_member. If omitted, it defaults to team_member.
At least one member is required.

Deleting a team

If only a team's scope or members have changed, rename the team and change its members instead of deleting it. Alert history, distilled knowledge, documents, and settings stay with the team.

Only organization owners and admins can delete a team. Before deleting:

Delete all of the team's schedules.
Transfer every document the team owns — including documents in the trash — to another team. In the delete dialog, select the documents with the checkboxes, choose the destination team, and transfer them. Transferred documents are searched by Buddy for the destination team's alerts right away.

Deleting a team also deletes its alerts and distilled knowledge. This cannot be undone.