> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/user-guide/project-dashboards.md).

# Project dashboards

In SonarQube Server 2026.5, dashboards enhance communication and collaboration among stakeholders by providing real-time visibility into the health and progress of your projects.

*Project dashboards are available starting in* [*Enterprise edition*](https://www.sonarsource.com/plans-and-pricing/enterprise/)*.*

You can use two built-in dashboards, the **Project health dashboard** and the **Security overview** dashboard, or create your own from scratch. Duplicating an existing dashboard gives you a good starting point for building a custom dashboard that fits your needs. Dashboards use interactive widgets to visualize different measures. You can then sort and filter the data, and click values in a dashboard to investigate further.

Dashboards include metrics related to dependency risks. Dependency risks are the security and compliance problems SonarQube Server detects in your project’s open source and third-party dependencies through [Software Composition Analysis (SCA)](/sonarqube-server/advanced-security/analyzing-projects-for-dependencies.md). To view dependency risks, you need [SonarQube Advanced Security](https://www.sonarsource.com/solutions/security/). See [Advanced Security](/sonarqube-server/advanced-security.md) for more information.

{% content-ref url="/pages/m86R4KhaTrdocqjPk8dg" %}
[Viewing and managing dashboards](/sonarqube-server/user-guide/project-dashboards/viewing-and-managing-dashboards.md)
{% endcontent-ref %}

{% content-ref url="/pages/3yyINHL8fDCy87uRW32J" %}
[Creating dashboards](/sonarqube-server/user-guide/project-dashboards/creating-dashboards.md)
{% endcontent-ref %}


---

# 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://docs.sonarsource.com/sonarqube-server/user-guide/project-dashboards.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.