> 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/2026.4/user-guide/managing-your-account/introduction.md).
# Introduction
Managing your SonarQube Server 2026.4 account.
As a SonarQube Server user, you have your own space where you can see information relevant to your account. To open this space:
1. Select your account menu in the top right corner of the SonarQube Server interface.
2. In the menu, select **My Account**. The **Profile** tab opens. It gives you a summary of the user groups you belong to and of the SCM accounts associated with your account (see [Viewing your user profile](/sonarqube-server/2026.4/user-guide/managing-your-account/viewing-user-profile.md)) and it allows you to disable the keyboard shortcuts.
3. Select the **Security** tab to manage authentication tokens or change your password.
4. Select the **Notifications** tab to subscribe to notifications.
5. Select the **Projects** tab to view the list of projects you are administering. You can select a project from here for full access.
---
# 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/2026.4/user-guide/managing-your-account/introduction.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.
