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

# Overview

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

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/10.8/instance-administration/authentication/saml/scim/scim-provisioning-with-azure-ad.md)
* [With Okta](/sonarqube-server/10.8/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 [Overview](/sonarqube-server/10.8/instance-administration/authentication/saml/overview.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 dynamically by asking a question.

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

```
GET https://docs.sonarsource.com/sonarqube-server/10.8/instance-administration/authentication/saml/scim/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.