Team Settings Reference

Open a team from Build → Teams. Its settings and members are edited on the Overview tab, below the summary cards. When you create a team, the same fields appear on the Create New Team form. For concepts, see Teams. For how each pattern uses these settings, see Team Orchestration Patterns.

Core fields

Field	Type	Default	Applies to	Description
Team Name	Text	—	All	Must be unique within the project.
Team Type	Select	Group Chat	All	Sequential, Concurrent, Group Chat, Group Chat Selector, Handoff or Magentic.
Interaction Mode	Select	Default (Supervised)	All	Default (Supervised), Supervised, Autonomous or Collaborative. See How people take part.
User Input Timeout (ms)	Number	30000 in the form	All	How long the team waits for a person's reply before carrying on. Must be zero or more. If it's empty or 0 when the team runs, 300,000 ms (5 minutes) is used. Tool approvals aren't affected by this timeout.
Introduction Message	Multiline text	Empty	All	The team's opening message.
Tags	Text, comma-separated	Empty	All	Labels for organising and searching.
Approval Override	Select	Inherit from risk appetite	All	Always require (pin) or Never require (pin) pins approval for every tool call made by any member. A team pin takes precedence over agent and function pins. A Never require pin can't switch off approval for critical-risk calls.
Enable Streaming	Checkbox	Off	All	Streams members' replies token by token. This replaces each member's own Streaming setting.

Context and history fields

Field	Type	Default	Applies to	Description
Selector Max History Messages	Number	10 when empty	Group Chat Selector	How many recent messages the coordinator reads when it picks the next speaker.
Max History Messages	Number	Empty	All	Stored on the team, but it currently has no effect on how much history members see.
Tool Summary Max Characters	Number	2,000 when empty	All	Tool results longer than this are saved to the session and replaced in the model's context by a short pointer, which the model reads with the result-reader tools. See Built-in Tools.

Interaction fields

These appear only after you pick an explicit Interaction Mode (anything other than Default (Supervised)). Each one overrides that part of the mode.

Field	Type	Mode default	Applies to	Description
Pause Between Turns	Checkbox	On for Collaborative, otherwise off	All	Pause after each member's turn. You can type continue (or send an empty message), type stop, or type anything else to steer. If you don't reply before the timeout, the team carries on.
Auto-approve Plans	Checkbox	On for Autonomous, otherwise off	Magentic	Approves the lead's plan automatically when plan review is enabled. Plan review can only be enabled through the API (enable_plan_review), so in teams created in the UI this setting has no effect.
User Input Handling	Select	Default	All	Default follows the mode. Wait for User waits for a person. Auto Respond answers input requests automatically.
Max Autonomous Responses	Number	5	All	How many automatic answers the team may give in a row before it stops. The count resets whenever a person replies.

Type-specific fields

Field	Type	Default	Applies to	Description
Max Rounds	Number	Empty (see right)	Group Chat, Group Chat Selector	The maximum number of turns. If empty, a Group Chat does one pass through the members when it's waiting for you, otherwise two passes. A Group Chat Selector allows three turns per member.
Tool Agent Extra Turns	Checkbox	Off	Group Chat (also shown for Group Chat Selector, where it has no effect)	Legacy turn order. The first two members speak, then only members that have tools take turns. If you have three or more members, members without tools after the second never speak. Leave it off unless you need that behaviour.
Max Stall Count	Number	5 when empty	Magentic	Rounds without progress before the lead replans.
Max Reset Count	Number	3 when empty	Magentic	How many full resets are allowed. A reset wipes the workers' memory of the task.
Max Round Count	Number	Unlimited when empty	Magentic	Total coordination rounds.
Execution Environment	Select	Project Default	All	Shown on the form, but not currently saved for teams. Set Execution Environment on each agent instead.

Members

Control	Applies to	Description
Assign Agents	All	Opens Assign Agents to Team. Search under Select Agents, choose one or more and click Assign. New members are added to the end. GitHub Copilot agents are disabled for Handoff teams.
Member chip / card	All	Shows each member. The delete icon removes the member after "Remove this agent from the team?".
Drag to reorder	Concurrent, Group Chat, Handoff, Magentic	Drag member cards into a new order. The order is saved straight away.
Role	Group Chat Selector	A per-member description that the coordinator reads to choose the next speaker. It replaces the agent's Default Role in this team. It's saved when you click Update.
User → and Agent → routing	Sequential	Routing fields that must be filled in before you can create a Sequential team. They're pre-filled when you choose Sequential. They don't change the run order, which is member order.

warning

Each Role field is filled from the agent's description when the team loads, not from the role you saved earlier. Check the Role fields before you click Update on a Group Chat Selector team.

Actions

Action	Description
Create Team	Creates the team and adds the members you selected.
Update	Saves changes to settings and roles.
Cancel	Discards unsaved changes.
Copy Team	Opens Copy Team. Enter a New Team Name (the default is the current name with "(copy)" added) and click Copy Team. The copy has the same configuration and members.
Publish Template	Platform administrators only. Publishes the team as a platform template. See Templates.
Delete	Asks "Delete this team?" first. Requires the project Admin role.
Active / Killed	Killswitch. Kill this team? offers Also terminate active chat sessions for this team. A killed team is read-only until you reactivate it.
Open in Chat	Starts a conversation with the team.

Tabs

Overview, Configure (currently empty), Topology, Tests, Observability, Risk, Controls and History. See Teams.

Fields available only through the API

Set these with PATCH /team-configurations/{id}, or with the Platform MCP server update_team tool.

Field	Description
coordinator_agent_id	Handoff: the member that starts. The default is the first member.
handoff_rules	Handoff: which members may hand off to which, as a map of agent name to a list of target names. The default is that every member can hand off to every other.
enable_plan_review	Magentic: pause for plan review before execution and after stalls.
suggested_prompts	One-tap opening suggestions for the team's chat.
path	Folder path in the Team Library.
Risk fields	risk_level, data_classification, risk_categories, compliance_tags, risk_notes, risk_owner, require_justification.

Related API endpoints

Method and path	Purpose
GET / POST /team-configurations	List or create teams. Creating requires the Editor role.
GET /team-configurations/search?field=&query=	Search by name, introduction_message, path or team_type.
GET / PATCH / DELETE /team-configurations/{id}	Read, update or delete a team. Passing agents on PATCH replaces the whole membership. Delete requires Admin.
POST /team-configurations/{id}/agents	Add several members, each {id or name, role_override}.
POST /team-configurations/{id}/agents/{agent_id}	Add one member, with an optional role_override.
PATCH /team-configurations/{id}/agents/{agent_id}/position	Set a member's position.
DELETE /team-configurations/{id}/agents/{agent_id}	Remove a member.
POST /team-configurations/{id}/risk-review	Record a risk review.

Related

• Teams
• Team Orchestration Patterns
• Agent Settings