Labels

Labels are first-class entities, not just strings. Each label has a module scope (TASK, PROJECT, WEBHOOK, and so on) and a color. Labels drive filters, automations (apply_label), and reporting cuts.

• Module-scoped uniqueness: the same name can exist on TASK and PROJECT
• Bulk-apply via the multi-select toolbar
• Color picker with a curated palette for accessibility

• Deleting a label detaches it from every entity; the history in the audit log still references the label id.
• Automation actions (apply_label) validate that the label exists at run time.

1. 1Go to Settings > Labels > New label.
2. 2Pick a module scope and color.
3. 3Apply the label via the task toolbar or the automation builder.

What does deleting a label affect?

Deleting detaches the label from every entity that carried it. The audit history still references the label by its identifier, so the record of what happened is intact, but the attachments are gone and recreating a label with the same name does not restore them.

Can the same label name exist twice?

Yes, once per module scope. A label named Urgent on tasks and a label named Urgent on projects are two different labels, because the uniqueness rule is per scope rather than global.

What happens to an automation that applies a label I have deleted?

The action validates that the label exists when it runs, so it fails cleanly rather than attaching something that is no longer there. Point the automation at a label that exists.