> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-mcp-bridge-private-server.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Coder connector

> C1 provides identity governance for Coder. Integrate your Coder deployment with C1 for unified visibility and governance over user access.

C1 provides identity governance for Coder. Integrate your Coder deployment with
C1 for unified visibility and governance over user access.

## Capabilities

| Resource | Sync                                                          | Provision |
| -------- | ------------------------------------------------------------- | --------- |
| Users    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

The connector reads the users of one Coder deployment. Each user syncs with
their username, full name, email, sign-in method, and the site-wide roles they
hold (such as Owner or User Admin). Active users sync as enabled; suspended and
dormant users sync as disabled, which is useful for offboarding review. Service
accounts are marked as non-human accounts so they can be filtered separately
from people.

## Gather Coder credentials

<Warning>
  To read every user, the token must belong to an account with the **Owner** or
  **User Admin** role. A token from a regular member can sign in but cannot list
  the full user roster.
</Warning>

<Steps>
  <Step>
    Sign in to your Coder deployment as a user with the Owner or User Admin
    role.
  </Step>

  <Step>
    Open your account's **Tokens** page and create a new token. Give it a long
    enough lifetime to keep the connector running, then copy the token value.
  </Step>

  <Step>
    Note the URL of your Coder deployment, for example
    `https://coder.example.com`.
  </Step>
</Steps>

## Configure the Coder connector

<Tabs>
  <Tab title="Cloud-hosted">
    Follow these instructions to use a built-in, no-code connector hosted by C1.

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Coder** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Coder connector.
      </Step>

      <Step>
        Set the owner for this connector.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Enter the Coder credentials:

        * **Deployment URL**: The base URL of your Coder deployment, for
          example `https://coder.example.com`.
        * **Session token**: The Coder API token you created.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Coder connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to run the Coder connector in your own
    environment.

    <Steps>
      <Step>
        Create secrets for the Coder credentials.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **Deployment URL**: The base URL of your Coder deployment, for
          example `https://coder.example.com`.
        * **Session token**: The Coder API token you created.
      </Step>

      <Step>
        Deploy the connector using your standard self-hosted connector process.
      </Step>
    </Steps>

    **Done.** Your Coder connector is now pulling access data into C1.
  </Tab>
</Tabs>