> ## Documentation Index
> Fetch the complete documentation index at: https://docket.hypertext.studio/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams

> The units that own work, each with its own workflow, cycles, and triage queue.

Support. Engineering. The Berlin chapter. One team is a completely normal number.

## What a team owns

<CardGroup cols={3}>
  <Card title="Workflow states" icon="list-check">
    Support runs Triaged → Waiting on customer → Resolved. Engineering names its own set. See
    [Labels and statuses](/docs/guides/concepts/labels-and-statuses).
  </Card>

  <Card title="Cycles" icon="rotate">
    Each team picks its own length. Support runs a month, Engineering runs two weeks. See
    [Cycles](/docs/guides/concepts/cycles).
  </Card>

  <Card title="Triage" icon="inbox">
    Docket lists new work here until someone files it.
  </Card>
</CardGroup>

## You cannot assign work to a team

You assign to a single **Actor**, one person or one agent. Every task has a short answer to "who
is doing this".

Leave work unassigned in the team's triage queue until you assign a person.

## Teams and tasks

Every Task belongs to a workspace **and** a team. The team gives it the statuses it moves through
and the triage queue it waits in.

A task's project is optional. Its team is required.

## Teams and permissions

A team is a valid target for a [grant](/docs/guides/concepts/workspaces#control-access).
Give "Volunteer" `contribute` on the Berlin chapter and `view` on Engineering, and each grant
applies to that team's work.

## Creating a team

Create and manage teams in **Settings → Members & Access**. Set workflow states in
**Settings → Statuses** and cycle cadence in the team's own settings.

<Tip>
  A team is for people who share a process. For a bounded piece of work, create a
  [Project](/docs/guides/concepts/projects).
</Tip>
