Labels

Labels are the last piece of workspace structure: where projects group tasks and goals tie them to outcomes, labels classify the tasks themselves so you can filter, scan, and pull together related work that does not share a project or a goal. A label is a named, colored tag — bug, urgent, customer-x — that you attach to tasks.

Labels are scoped to a project

A label belongs to a project within the workspace, which keeps each project's vocabulary its own. A project's labels reflect the way that work is actually categorized, without every workspace label being forced onto every project. A label has a name, a color, an optional description, and an order within its project's list.

When you create a label, Task Machine assigns it a color automatically so you do not have to pick one to get started, and you can override that color later. Today labels are created and maintained from the project management screens, where they live alongside the project's other settings — the dedicated label controls on the task views arrive with the task detail surfaces still being built out, so for now the project settings are where you manage them. Creating and editing labels requires the project-management permission, the same gate that governs the projects they belong to.

Archiving keeps a label out of the way without losing it

When a label has outlived its use, you archive it rather than delete it. An archived label stops appearing as a choice when you are tagging tasks, but it stays attached to the tasks that already carry it, so the history those tasks record stays intact and readable. You retire the vocabulary without rewriting the past.

That completes the structure your work lives in: a workspace holds members and the roles that govern them, teams group those members, projects contain the tasks, goals tie tasks to outcomes, and labels classify them. With the workspace set up, the next part of the journey is where you actually live day to day — the three surfaces. Continue to Discuss, Inbox, and Tasks.