> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/modeling-your-deployments/organization/labels.md).

# Labels

Labels allow you to create flexible taxonomies to slice and dice your DORA metrics across your Organization. They are used to combine any number of [projects](/sleuth-dora/modeling-your-deployments/projects.md) together for metrics comparison and trends.

Do you want to see how your Java-based projects compare to your Python-based projects? Perhaps you’d like to know how your TDD projects stack up against non-TDD projects. Are one week or two week sprints more efficient?

Group your projects by coding language, sprint time or whatever dimension you want insights on.

### Managing Labels

You can manage your Organization's Labels via your Organization settings. You can quickly label multiple projects via the create/edit Label dialog. Labels are a light-weight construct that instantly allow you to generate additional cross-project DORA metric Trends and Comparisons.

![](/files/9CnP4sc9eqtGRll0uA5t)

![](/files/bLp64Teyul9JBj2Z8U6C)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/modeling-your-deployments/organization/labels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.