# Notifications

To set the frequency with which the notification queue is processed, set the `sonar.notifications.delay` property (in seconds) in `<SONARQUBE_HOME>/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 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** > **General**.

**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.
