> 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/10.3/user-guide/user-account/overview.md).

# Overview

As a SonarQube Server 10.3 user, you have your own space where you can see the things that are relevant to you.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.3 documentation. For a list of all 10.3 pages, see the [SonarQube Server 10.3 page index](https://353248219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl622HnhaCz6xSuy6XTfl%2Fuploads%2FqlWPhmFHjpw7Xdej9zkF%2Fsonarqube-server-10.3-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.3 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

As a SonarQube Server user, you have your own space where you can see the things that are relevant to you.

## Profile <a href="#profile" id="profile"></a>

It gives you a summary of your:

* Login
* Groups
* SCM accounts

## Security <a href="#security" id="security"></a>

If your instance is not using a 3rd party authentication mechanism such as LDAP or an OAuth provider (GitHub, Google Account, …), you can change your password from here. Additionally, you can also manage your own authentication tokens.

You can create as many Tokens as you want. Once a Token is created, you can use it to perform analysis on a project where you have [Security](/sonarqube-server/10.3/instance-administration/security.md) permission.

## Notifications <a href="#notifications" id="notifications"></a>

Email notifications are managed here. It is possible to define your **Overall notifications**, settings applied to all projects. By default, email notifications are turned off.

To add **Notifications per project**, select **Add a Project** and **Search a project by name** in the search menu. Two additional notification option types, especially applicable to team projects, are available on the per-project level:

* Issues resolved as false positive or won’t fix
* New issues

## Projects <a href="#projects" id="projects"></a>

See **My Account** > **Projects** for a 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/10.3/user-guide/user-account/overview.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.
