Teams, Workflow & Labels

These settings define the structure your tasks live in: the teams, the board columns each team uses, and the labels and priorities available on tasks.

Teams

A team is a unit of work with its own board (for example Backend, Frontend, Design). Create teams in Settings; each new team gets a key (the prefix in task keys like BE-14) and appears in the sidebar with its board. A task always belongs to exactly one team.

Members

Each team has its own member roster — the people who belong to it — managed from the Members tab in that team's settings. Add anyone from your workspace to the team, or remove them; the change takes effect immediately. Every add and removal is recorded in the team's activity log, so there's a clear history of who changed the roster and when.

When you create a new team you're added to it automatically. Existing members were added to all of their teams when membership was introduced, so nothing anyone could previously see changed.

Workflow (board states)

Each team's board columns are its workflow states — for example Todo → In Progress → Review → Done. In a team's settings you configure that team's states: their names and order. Because workflow is per team, different teams can model their process differently (a simple Todo/Doing/Done, or a richer flow with review and QA). The states you define here are exactly the columns on that team's board and the status options on its tasks.

Labels

Labels are free-form colored tags used across tasks — for work type (bug, refactor), component (board, auth), or process state (needs-review). Manage the available labels (name and color) in Settings; once defined, they can be applied to any task.

Priorities

Priorities are a fixed set used everywhere: Critical, High, Medium, Low. They aren't configured — they're the standard scale described in "The Task in Detail".

Together these settings let each team work the way it wants while keeping tasks, labels, and priorities consistent across the workspace.