Teams | kanman documentation

A team is one AI team in kanman, bound to one tracker project and one or more repositories. See Teams for the concept. You manage teams in the app.

Your tools read teams through the REST API.

Teams in the app

Task	Where
See all teams with their status and active runs	Teams (`/<workspace>/teams`)
Create a team	Teams, New team. See Set up a team.
Open a team	Teams, the team (`/<workspace>/teams/<team>`): tabs Board, Runs, Reports, Settings

Read the policy

Open the team, then Settings (/<workspace>/teams/<team>/settings/autonomy). The policy is spread over the pages Autonomy, Limits and budgets, Hours and rhythm, Agent and models, Repositories and tracker, Chat and mentions, Knowledge, Checks and delivery, Code review, Services and on-call, Maintenance and CI and Team. Every member can read them; only admins can change them, and only the workspace owner can delete the team under Team (see Retention and deletion). Each key is described in Policy settings.

The MCP tool get_story also returns a summary of the policy that applies to a story.

Update the policy

Admins change the policy on the same pages; each change saves at once, with Undo. Pointing the trust dial under Autonomy at a preset first shows what would change, and Apply stores it. Changing a single setting away from the preset marks the policy as custom, and the dial shows “Balanced, adjusted”, for example. Every change is recorded in the audit log as policy_changed.

Two safety rules hold however you set the policy:

The acceptance spec folder .kanman/acceptance/** is always a denied path.
Turning off the acceptance spec requirement is only possible on the Trial preset.

Pause a team

Admins click the pause button next to the team’s status line in the team header. The pause takes effect at once, with Undo, and the header shows “Paused · Resume”. Running work finishes; nothing new starts until you resume. Admins can also ask kanman in the team’s intake (“pause the team”). Pausing is recorded as team_paused.

Resume a team

Admins click Resume in the team header, click Resume team on the card of the pause in the conversation, or ask kanman to resume the team. kanman picks up Ready stories again. Resuming is recorded as team_resumed.

REST API

List teams

GET /v1/teams returns all teams of the token’s workspace, sorted by name, with a summary of each team’s policy.

curl https://api.kanman.ai/functions/v1/api-gateway/v1/teams --header "Authorization: Bearer $KANMAN_API_KEY"

Field	Description
`id`, `slug`, `name`, `description`, `keyPrefix`	The team. `keyPrefix` is the first part of its story keys.
`paused`	`true` while the team is paused.
`policy`	`preset`, `custom`, `version`, `executor`, `maxConcurrency`, `budgets` (`runCents`, `dayCents`, `monthCents`), `planApproval`, `mergePolicy`, `pausedAt`, `updatedAt`. `null` for a team without a policy.
`createdAt`, `updatedAt`	Timestamps (ISO 8601).

Read a team

GET /v1/teams/{team} returns one team by its slug in the same shape. An unknown slug answers 404.

Changing a policy and pausing or resuming a team stay in the app, so every change goes through the same checks and audit entries.