Organization

Designate (or clear) a team lead

The structural gesture: a team's agents inherit this lead, so fifteen agents over three teams are three links to keep, not fifteen. lead: null clears the designation — the team then falls back to the company root, which is a warning (team-lead) and not an error. An agent may lead a team, but only if somebody is responsible for it in turn, otherwise the whole team would inherit a chain leading nowhere (ORG_NO_HUMAN_MANAGER).

put/organization/teams/{id}/lead

Request

  • Base URL: https://api.atako.ai
  • URL: https://api.atako.ai/organization/teams/{id}/lead
  • Auth: HTTP bearer

Path parameters

idstring uuid required

Team id

Request body

Response

The recomputed chart — identical shape to GET /organization/chart.

rootHumanIdstring uuid nullable required

DERIVED, never stored: the oldest admin member. Null when the company has no admin at all — the only case where the chart has nothing to hang on.

canEditboolean required

True when the caller is a company admin, i.e. when the write operations below are open to them. Told here so the client never has to deduce a permission from a 403 it provoked.

Changes

No recorded changes to this operation across all 2 revisions of this API.