> ## 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 an env0 connector

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

C1 provides identity governance for env0. Integrate your env0 organization with
C1 for unified visibility and governance over who belongs to your env0
organization, their email and organization role, whether their access is active
or still a pending invite, and when they last signed in.

## Capabilities

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

Each synced user carries their email, organization role, account status (enabled
or disabled), account type (human or API key), and last sign-in time.

## Gather env0 credentials

<Warning>
  To configure the env0 connector you need an env0 API key that can read your
  organization's users — an Organization Admin key, or a key whose role can list
  organization members.
</Warning>

<Steps>
  <Step>
    Sign in to env0 and open **Organization Settings**.
  </Step>

  <Step>
    Go to **API Keys** and create a new API key. Choose a key whose role can read
    the organization's users.
  </Step>

  <Step>
    Copy the **API Key ID** and the **API Key Secret**. env0 shows the secret
    only once, so store it when you create the key.
  </Step>

  <Step>
    Note your **Organization ID** — the organization UUID shown in Organization
    Settings.
  </Step>
</Steps>

## Configure the env0 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 **env0** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new env0 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 env0 credentials:

        * **API Key ID**: The ID of your env0 API key.
        * **API Key Secret**: The secret of that env0 API key.
        * **Organization ID**: Your env0 organization UUID.
      </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 env0 connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the env0 API Key ID and API Key Secret.
      </Step>

      <Step>
        Configure the connector with:

        * **API Key ID**: The ID of your env0 API key, supplied as a secret.
        * **API Key Secret**: The secret of that env0 API key, supplied as a secret.
        * **Organization ID**: Your env0 organization UUID.
      </Step>

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

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