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

# Set up a Unleash connector

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

C1 provides identity governance for Unleash. Integrate your Unleash
instance with C1 for unified visibility and governance over user access.

## Capabilities

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

The connector syncs users and groups, and resolves the group membership graph:
each group exposes a **member** entitlement, with grants linking groups to the
users who belong to them.

## Gather Unleash credentials

<Warning>
  You need an Unleash token whose owner holds the **Admin** root role. The admin
  user and group endpoints reject any token without it.
</Warning>

<Steps>
  <Step>
    Decide which token type fits your Unleash edition. On Unleash Open Source,
    create a **Personal API token** for an admin account. On Unleash
    Enterprise, create a **Service account** with the Admin root role and
    generate a token for it. The deprecated classic admin token also works but
    is not recommended.
  </Step>

  <Step>
    In Unleash, open the profile menu and go to **Settings** > **Personal API
    tokens** to create a personal token, or go to **Admin** > **Service
    accounts** to create a service account with the **Admin** root role and add
    a token to it.
  </Step>

  <Step>
    Copy the generated token. Also note the base URL of your Unleash instance —
    you will provide both when configuring the connector.
  </Step>
</Steps>

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

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

        * **Base URL**: The origin of your Unleash instance, with no trailing slash and no `/api/admin` suffix. For self-hosted Open Source use the bare origin, such as `https://unleash.example.com`. For Unleash-hosted, include the per-instance path segment, such as `https://eu.app.unleash-hosted.com/myinstance`.
        * **API token**: The Admin-root-role 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 Unleash connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector environment variables:

        * **UNLEASH\_BASE\_URL**: The origin of your Unleash instance (for example `https://unleash.example.com`), with no trailing slash and no `/api/admin` suffix.
        * **UNLEASH\_API\_TOKEN**: The Admin-root-role token you created (store this as a secret).
      </Step>

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

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