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

# SCIM with Okta

Learn how to configure Couchdrop to sync with Okta

## Overview

Couchdrop supports SCIM provisioning with Okta to keep users and groups synchronized between Okta and Couchdrop.

You can use Okta to provision and update Couchdrop users and groups, deactivate them when required, and optionally import existing Couchdrop users and groups into Okta.

### How provisioning works

Okta can provision users and groups into Couchdrop through the Couchdrop SCIM application.

Depending on the options you enable, Okta can:

* Create Couchdrop users
* Update existing users
* Deactivate users
* Push groups and group memberships
* Import existing Couchdrop users and groups back into Okta

This lets Okta act as the central identity management system while Couchdrop reflects the users and groups assigned through the SCIM integration.

{% hint style="info" %}
If you plan to import existing Couchdrop users or groups into Okta, you can configure this after the SCIM connection has been established.
{% endhint %}

## Configure SCIM provisioning

{% hint style="warning" %}

### Before you start

To configure SCIM provisioning between Couchdrop and Okta, you will need:

* Access to Couchdrop with permission to create a **User Provisioning Token**
* Administrator access to your Okta tenant
* The **Couchdrop SCIM** application from the Okta Application Catalog
* The users and groups you want to assign to the Couchdrop application in Okta
  {% endhint %}

{% stepper %}
{% step %}

### Create a User Provisioning Token in Couchdrop

In Couchdrop, navigate to **User Provisioning** and create a new **Provisioning Token**.

Copy the token. You will use it when configuring the Couchdrop SCIM application in Okta.
{% endstep %}

{% step %}

### Add the Couchdrop SCIM application in Okta

In Okta, navigate to **Applications** > **Applications**, then select **Browse App Catalog**.

Search for **Couchdrop SCIM** and select the application.

Select **Add Integration**, then select **Done**.
{% endstep %}

{% step %}

### Assign users and groups

Assign the users and groups that you want to provision between Okta and Couchdrop to the Couchdrop SCIM application.
{% endstep %}

{% step %}

### Configure the API integration

Open the **Provisioning** tab and select **Configure API Integration**.

Enable **API Integration**, then enter the Provisioning Token created in Couchdrop into the **API Token** field.

Select **Test API Credentials** to verify the connection.

If the test succeeds, select **Save**.
{% endstep %}

{% step %}

### Enable user provisioning

From the **Provisioning** settings, select **Edit** and enable:

* **Create Users**
* **Update User Attributes**
* **Deactivate Users**

These settings allow Okta to create, update, and deactivate corresponding users in Couchdrop.
{% endstep %}

{% step %}

### Configure group provisioning

To push groups and group memberships from Okta to Couchdrop, use the **Push Groups** option in the Couchdrop SCIM application.

Configure the Okta groups that should be pushed to Couchdrop.
{% endstep %}

{% step %}

### Configure imports from Couchdrop to Okta

If you want to import existing Couchdrop users and groups into Okta, open the **Provisioning** tab and select **To Okta**.

Configure the required scheduled import frequency and matching rules.

Then open the **Import** tab and select **Import Now**.

Okta will display the users and groups available for import. Select the users and groups you want to add to Okta, then select **Confirm Assignments**.
{% endstep %}
{% endstepper %}

## Supported features

<table data-search="false"><thead><tr><th width="206.89453125">Feature</th><th>Description</th></tr></thead><tbody><tr><td><strong>Push Users</strong></td><td>Users created in Okta are also created in Couchdrop.</td></tr><tr><td><strong>Push User Updates</strong></td><td>User updates in Okta are pushed to the corresponding Couchdrop users.</td></tr><tr><td><strong>User Deactivation</strong></td><td>Users deactivated in Okta are deactivated in Couchdrop.</td></tr><tr><td><strong>Push Groups</strong></td><td>Groups created in Okta are also created in Couchdrop.</td></tr><tr><td><strong>Push Group Updates</strong></td><td>Group updates in Okta are pushed to Couchdrop.</td></tr><tr><td><strong>Group Deactivation</strong></td><td>Groups deactivated in Okta are deactivated in Couchdrop.</td></tr><tr><td><strong>Import Users</strong></td><td>Users created in Couchdrop can be imported into Okta.</td></tr><tr><td><strong>Import Groups</strong></td><td>Groups created in Couchdrop can be imported into Okta.</td></tr></tbody></table>


---

# 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.couchdrop.io/administration/scim-and-sso/scim-with-okta.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.