> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/identity-providers-sso/configuring-scim-for-flosum.md).

# Configuring SCIM for Flosum

## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d) Overview

Flosum supports System for Cross-domain Identity Management (SCIM). SCIM is an industry-standard protocol that lets you provision, manage, and deprovision users in your Flosum tenant through Flosum's SCIM API. This automation streamlines user management and ensures consistency across your identity provider and Flosum.

{% hint style="info" %}
You can use JIT Provisioning as an alternative to SCIM, or combine the two. JIT Provisioning automatically creates and updates user accounts in Global Settings when users first log in via SSO. For more details, see the article below.

* [Configuring Just-In-Time (JIT) Provisioning](/global-settings/security/identity-providers-sso/configuring-just-in-time-jit-provisioning.md)
  {% endhint %}

## Flosum's SCIM API

Flosum's SCIM API is based on SCIM 2.0, an open standard for cross-domain identity management. It supports the User resource type, allowing you to perform various user management operations programmatically.

**Supported Actions**

* Retrieve all users
* Create new users
* Update users
* Activate or deactivate users
* Delete users

**Not Supported**

You cannot change a user's group through the SCIM API. However, when adding an identity provider in Global Settings, you can set it to automatically assign new users to a specific group.

{% hint style="info" %}

#### Flosum Username

In Flosum Cloud Apps, a user's email address serves as their username. When connecting an identity provider to Flosum's SCIM API, map the user's email address to the username attribute.
{% endhint %}

## **Supported Identity Providers**

Flosum supports automated user provisioning with the following identity providers. The articles below provide step-by-step instructions for configuring them to work seamlessly with Flosum's SCIM API.

* [Microsoft Entra ID - SCIM - Configuration](/global-settings/security/identity-providers-sso/scim-configurations/microsoft-entra-id-scim-configuration.md)
* [Okta - SCIM - Configuration](/global-settings/security/identity-providers-sso/scim-configurations/okta-scim-configuration.md)
* [PingOne - SCIM - Configuration](/global-settings/security/identity-providers-sso/scim-configurations/pingone-scim-configuration.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.flosum.com/global-settings/security/identity-providers-sso/configuring-scim-for-flosum.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.