> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Coder

> Connect your Coder account to Oleria to continuously discover user access across your cloud development environment platform.

Coder is a cloud development environment platform. Connect your Coder account to Oleria to bring user access into your identity and access graph.

## What Oleria discovers

User accounts and profile attributes synced from Coder's directory. Oleria uses this data for dormant account detection and access reviews, refreshed on Oleria's [regular sync schedule](/integrations/overview.md#sync-model).

## Prerequisites

* Admin access in Coder with permission to enable SCIM provisioning and generate a SCIM token.
* A Coder plan that includes SCIM provisioning (Premium license).
* Admin access on the Oleria platform to add a new integration.

> [!NOTE]
>
> Oleria must be able to reach your Coder host over HTTPS. Contact [support@oleria.com](mailto:support@oleria.com) to allowlist its exact hostname before you connect.

## Get your SCIM credentials from Coder

**1. Enable SCIM provisioning in Coder**

Sign in to Coder as an admin and turn on SCIM provisioning in the Coder deployment settings by setting CODER\_SCIM\_AUTH\_HEADER. Choose a long random value for the header; it is the bearer token Oleria sends.

**2. Copy your SCIM Base URL and Authentication Token**

Copy both values before you leave the page - you'll paste them into Oleria in the next section:

* **SCIM Base URL** - the SCIM 2.0 endpoint, `https://<your-coder-host>/scim/v2`.
* **Authentication Token** - the value you set in `CODER_SCIM_AUTH_HEADER`.

> [!NOTE]
>
> Copy the token now and store it securely. Rotate it per your organization's security policy.

## Connect Coder to Oleria

**1. Open the integration**

Go to your Oleria workspace, select **Integrations**, then select the **Coder** tile.

**2. Complete the connection form**

Fill in the connection form:

| Field | Notes |
| :- | :- |
| Instance Name | Optional. Short, recognizable label for this connection (for example, `coder-prod`). |
| SCIM Base URL | Required. The SCIM 2.0 endpoint copied from Coder. |
| Authentication Token | Required. The SCIM bearer token from Coder. |

**3. Save the integration**

Select **Connect** to validate the credentials and save the integration.

## Verify the integration

Confirm the new instance appears on the **Connected** tab of your Oleria **Integrations** page with a status of **Healthy**. Oleria syncs users from Coder on its [regular sync schedule](/integrations/overview.md#sync-model) once the initial sync completes.

> [!NOTE]
>
> If you regenerate the SCIM token in Coder, update the **Authentication Token** in Oleria by editing the integration.

## Remediation actions

Oleria can also take these actions in Coder when the SCIM token can update users:

* Enable or disable a user account
* Create a new user

> [!NOTE]
>
> Oleria doesn't check the SCIM token's permissions until an action runs. If an action fails, confirm the SCIM token can update users in Coder.

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.