> 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/viewing-projects/project-overview.md).
# Viewing analysis summary
In SonarQube Server 2026.5, view the analysis summary on the project summary page.
The project summary page allows you to view:
* The releasability status of the project.
* The current state of its quality.
* The quality of what has been produced since the start of your new code.
It answers two questions:
* Can I release my project today?
* If I cannot release it today, what should I improve to make the project pass its quality gate?
To open the project summary page:
1. Retrieve your project. See [Retrieving projects](/sonarqube-server/user-guide/viewing-projects/retrieving-projects.md) for more information.
2. Go to **Analysis** > **Summary**.
## Quality gate status
The quality gate is your most powerful tool to enforce your quality policy. If the project passes, the **Quality Gate Status** will show a simple, green all-clear banner. See [Understanding quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) for more information.
If not, details and drill-downs are immediately available to quickly identify what went wrong. A section for each error condition shows the current project value and what it should be. As usual, you’ll be able to click through on current values to get more details about each issue.
## Measures
On the **New code** and **Overall code** cards, you see all project measures. Select a measure for more details. Both list and tree views are available for each measure, and tree maps are available for percentages and ratings.
## Activity
This section contains the full list of code scans performed on your project since it was created in SonarQube Server. By going there, you can follow the evolution of the quality gate, see the changes in quality profiles, discover when a given version of your code has been scanned, and more.
See also [Viewing project activity](/sonarqube-server/user-guide/viewing-projects/activity-and-history.md).
## Related pages
* [Viewing project structure](/sonarqube-server/user-guide/viewing-projects/viewing-project-structure.md)
* [Managing your tokens](/sonarqube-server/user-guide/managing-tokens.md)
* [Using a project badge](/sonarqube-server/user-guide/project-badge.md)
* [Notifications](/sonarqube-server/user-guide/managing-your-account/subscribing-to-notifications.md)
* [Introduction](/sonarqube-server/user-guide/issues/introduction.md)
* [Managing Security Hotspots](/sonarqube-server/user-guide/security-hotspots.md)
---
# 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/viewing-projects/project-overview.md?ask=&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.
