> 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/2025.1/instance-administration/authentication/saml/scim/overview.md).

# Overview

SCIM helps you automatically provision user and groups to SonarQube Server 2025.1.

*Automatic provisioning through SCIM is available starting in* [*Enterprise edition*](https://www.sonarsource.com/plans-and-pricing/enterprise/)\*. \*

[SCIM](https://www.rfc-editor.org/rfc/rfc7644) is a protocol used to automatically manage user identity between an identity provider (IdP) and a service provider (SP, SonarQube Server in this context). If you manage permissions through groups, SCIM helps you automatically maintain user existence and permissions in SonarQube Server.

{% hint style="info" %}
For SCIM to work with SonarQube Server, the Identity Provider (IdP) needs to be able to access the SonarQube server, meaning it needs to be reachable from the IdP’s environment. This typically involves exposing the on-premise SonarQube instance to the IdP’s network, either directly or through a secure connection (e.g. public URL, provisioning agent).
{% endhint %}

You can enable SCIM to automate user and group provisioning in SonarQube Server. Supported operations from your IdP are:

* User creation
* User deletion
* Group creation
* Group membership addition and removal
* Group name update
* Group deletion

You can set up automatic provisioning between SonarQube Server and the following IdPs:

* [With Microsoft Entra ID](/sonarqube-server/2025.1/instance-administration/authentication/saml/scim/scim-provisioning-with-azure-ad.md)
* [With Okta](/sonarqube-server/2025.1/instance-administration/authentication/saml/scim/scim-provisioning-with-okta.md)

When you enable automatic provisioning through SCIM, all users and groups become read-only in SonarQube Server. The only operations available in SonarQube Server are local group deletion and local user deactivation (local meaning not managed by SCIM).

Note that before you can configure SCIM provisioning, you must configure SAML. See the SAML [Overview](/sonarqube-server/2025.1/instance-administration/authentication/saml/overview.md) page to get started with this configuration.


---

# 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/2025.1/instance-administration/authentication/saml/scim/overview.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.