# Associating with SCM account

As a System Administrator, you can explicitly associate an SCM (Source Control Management) account with a SonarQube user account.

{% hint style="info" %}
SonarQube Server users can view the SCM accounts associated with their account: see [viewing-user-profile](https://docs.sonarsource.com/sonarqube-server/2025.1/user-guide/managing-your-account/viewing-user-profile "mention").
{% endhint %}

## About the SCM account association <a href="#about-associated-scm-accounts" id="about-associated-scm-accounts"></a>

SonarQube Server associates users with SCM (Source Control Management) accounts to automatically assign issues to users:

* If SonarQube Server delegates the authentication to a third-party identity provider, this association is done through the delegation. However, you can associate the user with additional SCM accounts.
* If no delegation is used, SonarQube Server recognizes the SCM account from the SonarQube Servers account’s Login and/or Email address. If it cannot perform the association (or if you want to associate other SCM accounts with the user account), you can do it explicitly.

To add an SCM account to a SonarQube Server user account, you associate the SCM account’s login name or email address with the SonarQube Server account.

{% hint style="warning" %}
You should not associate the same SCM account with several SonarQube Server accounts; otherwise, SonarQube Server may not be able to properly assign issues to SonarQube Server users. In particular, this means that you should not configure the same email address in several SonarQube Server user accounts (Note that the email address check is case-insensitive in SonarQube Server). To ensure a proper issue assignment, SonarQube Server may reject a user login attempt, for example, if a SAML user logs in with an email address that is associated with a local user (In this case, the error "This account is already associated with another authentication method" is raised).
{% endhint %}

## Adding an SCM account to a SonarQube Server user account <a href="#adding" id="adding"></a>

1. Got to **Administration > Security > Users** and [viewing-users](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/user-management/viewing-users "mention").
2. In the user’s **Actions** column, select the three-dot menu.
3. Select **Update (SCM) details**.
4. Near **SCM Accounts**, select **Add**. A box is displayed.
5. In the box, enter the SCM account’s login or email address.
6. To add another account, re-select **Add**, etc.
7. Select **Update**. The added SCM accounts are displayed in the **SCM Accounts** column as illustrated below.

![](https://3560343708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4FzELVjsPO4ijRo3jtBV%2Fuploads%2Fgit-blob-a2efabdb70edd899da77b63eb0b39d1e2b05e48e%2F2dcc8637616d4c932c733e89e576280b99c762ff.png?alt=media)

## Related pages <a href="#related-pages" id="related-pages"></a>

* [viewing-users](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/user-management/viewing-users "mention")
* [overview](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/authentication/overview "mention")
* [solution-overview](https://docs.sonarsource.com/sonarqube-server/2025.1/user-guide/issues/solution-overview "mention")
* [overview](https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/authentication/overview "mention")


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.1/instance-administration/user-management/updating-scm-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
