> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/tags.md).

# Tags

## What tags help you do

Tags make workflows easier to sort, review, and reuse.

They work best when your team needs to answer simple questions fast:

* Who owns this workflow?
* What is it used for?
* Is it ready to use?

<figure><img src="/files/EZE1djTN8UV4YziikuG7" alt=""><figcaption></figcaption></figure>

### When to use tags

Use tags when you have:

* many workflows in one workspace
* multiple teams sharing the same library
* draft, active, and review workflows at the same time

Tags are especially useful for operations, marketing, support, and internal tools.

### A simple tagging system

Start with three tag groups only:

* **Team:** `Sales`, `Marketing`, `HR`
* **Purpose:** `Lead capture`, `Reporting`, `Support`
* **Status:** `Draft`, `Needs review`, `Approved`

This is enough for most teams.

Avoid creating too many tags too early.

### Examples that work well

Here are a few strong examples:

* `Marketing` + `Campaign reporting` + `Approved`
* `Support` + `Ticket triage` + `Needs review`
* `HR` + `Onboarding` + `Draft`

These labels are short and easy to understand.

### Tagging rules for teams

Keep tags useful by setting a few basic rules:

* Use short names
* Use one meaning per tag
* Agree on the same spelling across the team

For example, pick one format and keep it:

* `Needs review`
* Not both `Review` and `Need review`

### What to avoid

Avoid tags that do not help people make a decision.

Examples to avoid:

* `Workflow`
* `Important`
* `Test 2`

These tags add noise.

They do not help people find the right workflow.

## Recommended review habit

Review tags whenever you:

* Publish a workflow
* Hand a workflow to another team
* Turn a workflow into a template

This keeps your library clean over time.

### Next steps

* Standardize workflow naming in [Manage a workflow](/workflow-builder/manage-a-workflow.md).
* Prepare reusable assets in [Create template](/workflow-builder/create-template.md).
* Keep the canvas readable in [Appearance](/workflow-builder/appearance.md).