> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/administration/provisioning-scim.md).

# Automatic collaborator provisioning (Provisioning / SCIM)

### What is provisioning?

Provisioning (supply) is the automatic, continuous synchronization of users from an identity provider to Steeple. Unlike SSO, which only acts at authentication, provisioning keeps data up to date at all times.

#### What is automatically synchronized

* **Identity data** : first name, last name, email
* **Access rights** to Communities
* **Role assignment**

#### Protocol

Steeple uses the **SCIM** (System for Cross-domain Identity Management). Communication is **one-way** : from the identity provider to Steeple.

#### Synchronized resources

* Users
* Groups
* User-group memberships

### Important prerequisite

The **SSO must be configured before provisioning**. It is not possible to configure provisioning on its own, regardless of the provider.

### Supported providers

* **Azure Active Directory** (Microsoft Entra ID)
* **Okta**

Google Workspace only supports SSO, not SCIM provisioning.

### Group mapping → Communities

The identity provider's groups do not directly match Steeple Communities. An **intermediate association** is required: each group is linked to a pair (community, role), which translates group membership into community access with a specific role.

**Recommendation** : create at least **two groups per community** (contributors and administrators).

### Configure provisioning

The setup is done from **Administration** > **Integrations** (`/administration/integrations`).

#### Provisioning with Azure Active Directory

1. In Steeple: Administration > Integrations > Install > click "Show" in the Identity section to get the**SCIM URL** and the **Bearer Token**
   * The token is a secret: never share it in an unsecured channel (chat, email, public ticket)
2. In Azure: Directory Overview > Provisioning > switch to mode **Automatic**
3. Paste the URL (Tenant URL) and the Token (Secret Token), test the connection
4. If soft-delete is needed: add an expression mapping `Switch([IsSoftDeleted], , "False", "True", "True", "False")` on the attribute **active**
5. Assign the pre-created groups in "Users and Groups"
6. Start provisioning — **Azure syncs every 25 to 40 minutes**
7. In Steeple: assign roles to the linked groups and Communities
8. Check that the number of users and groups matches, then enable synchronization

#### Provisioning with Okta

1. In Steeple: Administration > Integrations > Okta SCIM > Install to get the**Tenant URL** and the **Secret Token**
   * The token is a secret: never share it in an unsecured channel (chat, email, public ticket)
2. In Okta: General > App Settings > manually enable provisioning > save
3. Provisioning > Integration > configure the SCIM connector:
   * Paste the Tenant URL
   * Unique identifier: **userName**
   * Check only the boxes **Push**
   * Authentication mode: **HTTP Header** with the Secret Token
   * Test then save
4. Provisioning > Settings > To App : enable **Create Users**, **Update User Attributes**, **Deactivate Users**
5. Assign users/groups, configure Push Groups for mapping to Communities
6. Enable synchronization in Steeple — **Okta applies changes almost immediately**

### Important warnings

* **Disabling or deleting a user** on the identity provider side **removes the user from the Steeple organization** and makes their Posts invisible
* Only manual support intervention can reassign the Posts of a removed user
* Any user absent from the company Directory will have **all their access removed** by default

### Additional options

* **Automatic sending of invitation emails** to newly created users (optional with SSO, since SSO allows login without an invitation)
* **Manual account creation** outside the company Directory (these accounts use classic email/password authentication and must be deleted manually)

### Specific case

If you can't find one of your employees in the Steeple Directory, check in your identity provider (Entra-Okta...):

* that your employee is indeed present
* that the user is indeed linked to a group that grants access to the Steeple application

### What the assistant can do

The assistant can guide the user to the page **Integrations** via navigate\_to and explain provisioning concepts. For detailed technical setup, direct them to <https://help.steeple.com/>
