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

# Set up a Split connector

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

C1 provides identity governance for Split. Integrate your Split organization
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 syncs the users of a single Split organization as user
identities. Each user carries their account status (active or deactivated),
whether two-factor authentication is enabled, and the groups they belong to, so
you can see who has access to your Split organization and how they are secured.

## Gather Split credentials

<Warning>
  You need a Split **Admin API key**. It grants organization-wide management
  access, so treat it as a secret. An SDK key will not work — the Admin API
  requires an Admin key.
</Warning>

<Steps>
  <Step>
    Sign in to Split as an administrator of the organization you want to sync.
  </Step>

  <Step>
    Open **Admin settings**, then go to the **API keys** area.
  </Step>

  <Step>
    Create a new key and choose the **Admin** key type. Give it a descriptive
    name and copy the generated key — you will not be able to see it again.
  </Step>
</Steps>

## Configure the Split 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 **Apps** > **Connectors** and click **Add connector**.
      </Step>

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

      <Step>
        Choose where to add the connector: **Create a new app**, or **Add to an existing app** (then select the app).

        If you're creating a new app, choose whether to link it to an application discovered from your identity provider: select **Yes** and pick the IdP application, or **No** to continue with just the connector.
      </Step>

      <Step>
        Set the connector's **Name** and, optionally, a **Description**.
      </Step>

      <Step>
        Click the pencil icon next to **Owners** to choose who can configure and manage this connector.
      </Step>

      <Step>
        Click **Add**. The connector is created and its configuration page opens.
      </Step>

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

      <Step>
        Enter the Split credentials:

        * **Admin API key**: The Admin API key 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 Split connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the Split Admin API key.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_SPLIT\_ADMIN\_API\_KEY**: The Split Admin API key (store this as a secret).
      </Step>

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

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