Labels

Labels are named, coloured tags that belong to the workspace. Each label belongs to one module, such as tasks or projects, and has a colour from a ready-made palette. Owners and administrators create, rename, recolour and delete labels in Settings, Labels. You attach a label to a task in its detail drawer, and an automation can attach one with the apply label action.

• Module-scoped uniqueness: the same name can exist on TASK and PROJECT
• Pick the colour of each label from a ready-made palette
• Attach labels to a task from the Labels field in its detail drawer

• 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. 1Open Settings, then Labels, and choose the module tab, such as Tasks.
2. 2Enter a tag name, pick a colour and choose Create tag.
3. 3Open a task and add the label in the Labels field of its detail drawer, or choose the apply label action in an automation.

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.