> 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.3/project-administration/managing-project-tags.md).

# Managing project tags

In SonarQube Server 2025.3, project tags allow you to categorize and group projects for easier selection on the Projects page.

To manage the tags of your projects:

1. Retrieve your project. See [Retrieving projects](/sonarqube-server/2025.3/user-guide/viewing-projects/retrieving-projects.md) for more details.
2. In the top right corner, select **Project Information**.
3. In the **Tags** section left panel, select the plus sign to assign a new tag to the project. A window pops up with the list of existing tags.
4. In the list, select the tag(s) you want to assign.
5. To create a new tag, enter it in the **Search for tags…** field, and select it in the list.

<figure><img src="https://2741114604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4vN6mMcoPndARxvycboz%2Fuploads%2Fgit-blob-b10295559f23033939aeab5d62bf2f0190180852%2Fsonarqube-project-tags.png?alt=media" alt="Adding tags on the project information page"><figcaption></figcaption></figure>


---

# 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.3/project-administration/managing-project-tags.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.