> 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.5/instance-administration/notifications.md).

# Notifications

Everything to know about configuring SonarQube Server 10.5 email notifications.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.5 documentation. For a list of all 10.5 pages, see the [SonarQube Server 10.5 page index](https://3691828591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feu7dHWcqP9Cr3eUAzwWg%2Fuploads%2FjUvEoDEUUE0rAURT5wZJ%2Fsonarqube-server-10.5-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.5 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

To set the frequency with which the notification queue is processed, set the `sonar.notifications.delay` property (in seconds) in `<sonarqubeHome>/conf/sonar.properties`. The server must be restarted for the new value to be taken into account.

## Who gets notifications <a href="#who-gets-notifications" id="who-gets-notifications"></a>

For notifications related to code quality, only users who subscribe themselves will get notifications. With only one exception, there is no admin functionality to proactively subscribe another user. If you believe a user should be receiving notifications, then you must notify the user that they should subscribe.

### The exceptions <a href="#the-exceptions" id="the-exceptions"></a>

**Quality profiles**

Notifications will automatically (without user opt-in) be sent to users with Quality Profile Administration rights when built-in quality profiles are updated. These updates can only happen through updating SonarQube Server or updating a third-party analyzer. This type of notification is on by default, and can be toggled globally in **Administration** > **Configuration** > **General Settings** > **General** > **Quality Profile**.

**Tokens**

Notifications will automatically (without user opt-in) be sent to users when their tokens are about to expire.

## Email configuration <a href="#email-configuration" id="email-configuration"></a>

To configure the email server, go to **Administration** > **Configuration** > **General Settings** > **General** > **Email**.

Check also the Server base URL property at **Administration** > **Configuration** > **General Settings** > **General** > **General** to make sure that links in those notification emails will redirect to the right SonarQube Server URL.


---

# 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.5/instance-administration/notifications.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.