> 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/projects.md).

# Projects

**Projects** are the main container that Sleuth uses to organize your deployments. For example, a project can correlate to a product that your company offers, a collection of micro services or any collection of [deployments](/sleuth-dora/modeling-your-deployments/code-deployments.md), [environments](/sleuth-dora/modeling-your-deployments/environment-support.md) and [impact sources](/sleuth-dora/settings/project/impact.md) that model how you work.

A project gives you a high-level view your Accelerate (DORA) metrics and of all the changes and deploys happening within. With your project you can:

* See, at a glance, if it's safe to deploy your next change
* Track your Project's DORA metrics (deploy frequency, change lead time, change failure rate, MTTR and deploy size)
* Filter Project-level DORA metrics by specific Code deployments, environments, and contributing [Teams](/sleuth-dora/modeling-your-deployments/teams.md)
* Know the latest change made to each deployment and it's drift from your other environments
* Slice and dice your past deploys via a [powerful search](/sleuth-dora/modeling-your-deployments/code-deployments/search.md)
* Configure Slack or Email deploy [notifications for your team or individuals](/sleuth-dora/notifications.md)
* Know the health and Impact of your deploys via your key SLIs

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2Fyvt3BeduB3bB643O54ib%2Fimage.png?alt=media&amp;token=e4828864-accd-4024-8356-03f32f3e320c" alt=""><figcaption><p>Metrics dashboard for a specific Project</p></figcaption></figure>

<figure><img src="https://2832637360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1bR_-Od0islbiOl4G0%2Fuploads%2FiNvj97G9otKzS2ed1tOz%2Fimage.png?alt=media&amp;token=f08d7387-d1cb-49a9-962a-893cb9ef2377" alt=""><figcaption><p>Status dashboard for a specific Project</p></figcaption></figure>

## Further Reading

For additional information on how Sleuth calculates and presents "percent change" for the Project Metrics dashboard for other dashboards and views, see [Interpreting "Percent Change" in Sleuth](/sleuth-dora/accelerate-metrics/how-we-calculate.md#interpreting-percent-change).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.