# List the workspace's teams (read-only — auth owns the entity)

The teams of the caller's active workspace that the CALLER IS IN — the teams named by the teams[] claim in their token, not every team the workspace has. Callers holding org.data.read_all (owner, admin) get the whole workspace instead, so leadership is never locked out. Personal workspaces are never narrowed: they have one member and one tasks-local container.
May be EMPTY, and an empty list is not an error: it means the caller is in no team yet. Clients must render that as its own state rather than as "no teams exist" — the workspace may be full of teams the caller cannot see. Membership changes reach this list when the token re-mints (<=1h, immediately on a workspace switch), so a just-created team can be missing from one request and present in the next.
The team ENTITY is platform-wide (the same team Accounts manages, owned by the auth service), but this endpoint reads tasks' OWN copy, replicated from the platform event stream. It makes no call to auth, so auth being unreachable no longer empties this list. A team created in Accounts appears here within seconds, with a minted issue-key prefix and the default workflow.
A team DELETED in Accounts leaves this list, while its issues stay readable by direct reference — deleting a team must not destroy the work filed under it.

Canonical: https://easerix.com/docs/developers/api/tasks/teams/listTeams

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

export default function Layout(props) {
  const { APIPage, OpenAPIPage } = props.components ?? {};
  // "APIPage" is the old name from v10, this allows both for backward compatibility
  const Comp = OpenAPIPage ?? APIPage;
  return (
    <>
      {props.children}
      <Comp document="tasks" operations={[{"path":"/v1/teams","method":"get"}]} />
    </>
  );
}