> 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/2025.6/user-guide/viewing-projects/viewing-project-structure.md).

# Viewing project structure

In SonarQube Server 2025.6, the Code page shows your project's structure.

You can view the project’s structure and code in SonarQube Server. For private projects, you need the **Browse** and **See Source Code** permission.

To view the structure and code of a project:

1. Retrieve your project. See [Retrieving projects](/sonarqube-server/2025.6/user-guide/viewing-projects/retrieving-projects.md) for more information.
2. In the project navigation bar, select **Code**. It takes you to an outline of your project structure.
3. Drill down to see files in a directory, and select a file to see its code.

{% hint style="info" %}
If your project is too large for easy exploration via drilling, the search feature on this page will help. While the global search in the main menu returns results from throughout the SonarQube Server instance, the localized search on the code page is restricted to files and directories in the current project.
{% endhint %}


---

# 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/2025.6/user-guide/viewing-projects/viewing-project-structure.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.