> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/account-setup-and-administration/managing-your-org/user-provisioning.md).

# User Provisioning

SCIM enables automatic provisioning and de-provisioning of users in Docupilot through your identity provider (IdP).

## Prerequisites

Ensure you have&#x20;

* SSO is configured for your Organization
* You have admin access to your identity provider (e.g., Okta, Azure AD)
* SCIM provisioning is enabled in your Docupilot account

To get started, navigate to **Organization Settings > Security > User Provisioning.**

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FQsS9j2tIr0RiGQhWL60x%2FScim.gif?alt=media&amp;token=c5817b54-98bc-4b64-b199-e3b2a7e52b55" alt=""><figcaption></figcaption></figure>

## Manual Provisioning

Users are created when they sign in for the first time using SAML SSO. This is the default provisioning method.

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FE4SHMqKan9bJbz31NMN3%2FMannual%20Provisioning.png?alt=media&amp;token=b0bdc4c3-1aa2-4024-815a-46cfec9472a6" alt=""><figcaption></figcaption></figure>

## SCIM Provisioning

Follow the steps below to configure SCIM provisioning:

#### Step 1: Generate API Key in Docupilot

<div align="left"><figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2Fkq0FGbZ9GWkqpvvUmbck%2FD1.png?alt=media&amp;token=5b3cc5bd-0df4-414b-90c9-55ca90413ad7" alt="" width="563"><figcaption><p>Configuring User Provisioning in Docupilot</p></figcaption></figure></div>

1. Navigate to **Organization Settings** > **Security** > **User Provisioning**.
2. Click **Create API Key** to generate a SCIM API key.<br>

   <figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2Fsc3q43pJb2BHutSWGJVR%2FD2.png?alt=media&amp;token=c75adde9-a9cb-451f-8ef0-ca2749fb1301" alt=""><figcaption><p>Creating API Key in Docupilot</p></figcaption></figure>
3. Copy and securely store the **API Key**. This key is displayed only once and will be required for next steps.<br>
4. Click **I’ve saved it** after securely storing the API key.<br>

   <figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FhLhkm6E2EinwdqR4xFV8%2FD3.png?alt=media&amp;token=aa8f649c-1f0b-4034-a8ea-67d3435e0b0d" alt=""><figcaption><p>Enable SCIM in Docupilot</p></figcaption></figure>
5. Click **Enable SCIM**.

#### Step 2: Configure your Identity Provider (IdP) & Enable Provisioning

{% tabs %}
{% tab title="Okta" %}
**Configure API Integration**

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FqYNz4H8ZY6aCsui9QHIu%2FConfigure%20API%20in%20Okta.png?alt=media&amp;token=78ba202f-6ad0-4d68-a143-ad3a8ec98624" alt=""><figcaption></figcaption></figure>

In your Okta application navigate to Docupilot:

* Go to the **Provisioning** tab
* Click **Configure API Integration**
* Select **Enable API Integration**
* UnSelect **Import Groups**
* Paste the API Key generated in Docupilot in the **API Token** Field
* **Test API Credentials** and Click **Save**.

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FMX6rYScm1gBWScna9zCB%2Fimage%20(16).png?alt=media&amp;token=a658be11-9418-4665-a400-0ca7af206581" alt=""><figcaption><p>Enabling API Integration in Okta</p></figcaption></figure>

**Enable Provisioning Actions**

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FZIUWCWPmHao4emqazllN%2FEnabling%20Provisionsss.png?alt=media&amp;token=0a255e40-9ea1-4f85-991e-d857f2473b99" alt=""><figcaption></figcaption></figure>

After saving the API integration, enable the required provisioning actions:

* Create Users
* Update User Attributes
* Deactivate Users
* Click **Save** after enabling the required options.
  {% endtab %}

{% tab title="Microsoft Entra ID" %}
**Create a Provisioning Configuration in Microsoft Entra ID**

<div align="left"><figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2Fi5fH5mhZH2zfsrnr2tFi%2FE1.png?alt=media&amp;token=7ac4a559-d96d-46d5-9b21-1aa26bf720dc" alt="" width="563"><figcaption></figcaption></figure></div>

1. Open your **Docupilot Enterprise Application** in Microsoft Entra ID.
2. Navigate to Provisioning.<br>

   <div align="left"><figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FyXFkNQGkDkYZClLDRiNo%2FE2.png?alt=media&amp;token=c9df754a-2d7e-4c04-be68-4d7d988183db" alt=""><figcaption><p>Adding New Configuration for User Provisioning in Microsoft Entra ID.</p></figcaption></figure></div>
3. Click New configuration.<br>

   <figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2F5I44cZ0Rba5E5yM3Dpqt%2FE3.png?alt=media&amp;token=1bccc9e4-abe4-4c0d-8287-82bbe1dd579b" alt=""><figcaption></figcaption></figure>
4. Select **Bearer authentication** as the authentication method.
5. Copy-Paste the **SCIM Base URL** from Docupilot into the **Tenant URL** field.
6. Paste the **API Key** from Docupilot into the **Secret token** field.
7. Click **Test connection** to verify the configuration.
8. Once the connection is successful, click **Create**.

**Start Provisioning**

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2FQ28vTd4ECoJUWxBjIEd0%2FE4.png?alt=media&amp;token=b6a31a17-2fa6-46df-808c-87da7d842836" alt=""><figcaption></figcaption></figure>

1. Return to the Provisioning page in Microsoft Entra ID.
2. Click **Start provisioning** to begin synchronizing users and groups with Docupilot.
   {% endtab %}
   {% endtabs %}

#### Step 4: Assign Users

Assign users or groups to the Docupilot application in your IdP to start provisioning.


---

# 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://help.docupilot.app/account-setup-and-administration/managing-your-org/user-provisioning.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.
