> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/workspace/scim-and-rbac.md).

# SCIM & RBAC

SCIM automates admin provisioning and role management. Connect your identity provider to create, update, and suspend console accounts, sync attributes in real time, and map IdP groups to Siit roles

SCIM (System for Cross-domain Identity Management) automates admin provisioning and role management for your Siit console. Connect your identity provider to automatically create, update, and suspend user accounts—no manual account management needed.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FbJJTlrR9Iu3E9zyZkjue%2FCleanShot%202026-01-13%20at%2010.52.21.png?alt=media&amp;token=c043f4ab-1962-4193-84ad-9250b2c4976b" alt=""><figcaption></figcaption></figure>

#### **What you get:**

* **Automatic user provisioning** – new employees get Siit access as soon as they're added to your directory
* **Real-time attribute sync** – job titles, phone numbers, and languages stay current
* **Group-to-role mapping** – assign Siit permissions based on your existing IdP groups
* **Instant deprovisioning** – suspended or deleted accounts lose access immediately

SCIM ensures your team's access stays perfectly in sync with your organization's directory, reducing security risks and IT overhead.

***

#### **How it works**

When SCIM is enabled, your identity provider becomes the source of truth for Siit access:

1. **User lifecycle** – accounts are created when users are assigned the Siit app in your IdP, updated when attributes change, and deactivated when unassigned
2. **Attribute sync** – user details (name, email, title, phone, language) sync automatically from your directory
3. **Role mapping** – link IdP groups to Siit roles so permissions are assigned automatically based on group membership

**Supported providers:**

* Okta ([full setup guide available](https://help.siit.io/okta-scim-setup))
* Jumpcloud ([Setup Guide](https://help.siit.io/how-do-i-set-up-scim-provisioning-with-jumpcloud))
* Other SCIM 2.0 compatible providers

***

#### **What syncs**

SCIM synchronizes these user attributes from your identity provider:

* Username
* Email address
* Job title
* Primary phone number
* Preferred language

Role assignments sync through group mappings you configure in your IdP.

***

#### **Group-to-role rules**

A Siit account holds one role, so keep each person in a single Siit group on your IdP. Adding someone to a group gives them that group's role, whatever role they had before — a move between two admin roles works whichever order your IdP sends the changes in.

Two things SCIM will not do:

* **Change the Owner.** Any call that would move, demote, duplicate, deactivate or delete the Owner is refused and nothing in it is applied. Ask Siit support to change the Owner.
* **Accept a member it doesn't know.** A group change naming an unknown member is refused whole, so the group is never half-applied. A group name that already exists is refused too, rather than quietly merged.

Admin seats are bought automatically, once every person joining has been accepted.


---

# 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.siit.io/workspace/scim-and-rbac.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.
