> 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-cloud/administering-sonarcloud/managing-organization/creating-organization/security-contact.md).

# Security contact

As an administrator of your organization you can set up a dedicated contact for urgent, security-related communications.

## Overview

As an organization administrator, you can manage the security contact for your SonarQube Cloud organization. This email address is designated for organization-level security alerts, such as official security advisories or notifications regarding data breaches and infrastructure incidents.

This contact is strictly for platform integrity communications and does not receive code analysis scan results. See [Subscribing to email notifications](/sonarqube-cloud/managing-your-account/notifications.md) for more information about how to set up notifications for analysis-related and background task events.

## Permissions

You need the Administer Organization permission to set up the security contact for an organization. To change the permissions, select your organization from the **Account** menu and go to **Administration** > **Permissions** to apply the permission to users or groups.

## Setting up the security contact email address

To set up the security contact email address:

1. Select your organization from the **Accounts** menu.
2. Go to **Administration** > **Organization settings** > **Security contact**.
3. Click on **Add email** and enter the email address for your security contact.
4. Click **Save**.

{% hint style="info" %}
Sonar recommends that you use a distribution list or group alias, for example <securityteam@yourcompany.com>, for the security contact email.
{% endhint %}

Once you have saved the security contact email address, you can **Edit** it, or delete it. Additionally, the entry shows the email address of the user who set up the security contact and the date when it was updated.

## Related pages

* [Managing organization permissions](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-permissions.md)
* [Changing organization settings](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/changing-organization-settings.md)
* [Subscribing to email notifications](/sonarqube-cloud/managing-your-account/notifications.md)


---

# 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-cloud/administering-sonarcloud/managing-organization/creating-organization/security-contact.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.