> 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/instance-administration/user-management/updating-scm-details.md).
# Associating with SCM account
As a System Administrator, you can explicitly associate an SCM (Source Control Management) account with a SonarQube Server 2026.5 user account.
{% hint style="info" %}
SonarQube Server users can view the SCM accounts associated with their account: see [Viewing your user profile](/sonarqube-server/user-guide/managing-your-account/viewing-user-profile.md).
{% endhint %}
## About the SCM account association
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
1. Go to **Administration** > **Security** > **Users** and retrieve the user (see [Viewing user accounts](/sonarqube-server/instance-administration/user-management/viewing-users.md)).
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.
The figure below shows:
1. The user's login name and email address.
2. The login name or email address added to the user account as *SCM account*.
## Related pages
* [Viewing user accounts](/sonarqube-server/instance-administration/user-management/viewing-users.md)
* [SonarQube analysis process](/sonarqube-server/discovering/analysis-overview/process-steps.md#automatic-issue-assignment)
* [Overview of authentication and provisioning](/sonarqube-server/instance-administration/authentication/overview.md#local-user-concept)
---
# 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/instance-administration/user-management/updating-scm-details.md?ask=&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.
