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.
`bundle_settings`	object	No	—	Alert bundling settings for the Team. Edited through the dedicated Bundle Settings editor.

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.