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

# Set up LaunchDarkly connector

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

## Capabilities

| Resource  | Sync                                                          | Provision                                                     |
| :-------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Member    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Base role | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Role      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Team      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

**Additional functionality:**

* Create and delete members.
* Assign and unassign a base role (`reader`, `writer`, `admin`, `no_access`) on members. Unassign sets the member to `no_access`. Owner-role transfer is not exposed; it requires LaunchDarkly's UI-only reauthentication flow.
* Grant and revoke custom-role assignments on members.
* Add and remove members from teams.

LaunchDarkly has no separate disabled or deactivated member state, so the connector maps a disable request to deletion. Provisioning through this connector isn't supported on LaunchDarkly accounts that have SCIM provisioning enabled; manage LaunchDarkly members through your identity provider instead.

## Gather LaunchDarkly configuration information

Configuring the connector requires you to pass in information from LaunchDarkly. Gather these configuration details before you move on.

Here's the information you'll need:

* API Access Token

See the LaunchDarkly docs for information on how to acquire credentials: [View the documentation](https://launchdarkly.com/docs/home/account/api-create#create-access-tokens)

This connector requires an access token with one of the following permission sets:

* **Reader** base role (sufficient for read-only sync of members, teams, and custom roles).
* **Admin** base role (or a custom role granting `createMember`, `updateMember`, and `deleteMember` on `member/*`) is required to also use the member create / delete and custom-role grant / revoke capabilities.

## Configure the LaunchDarkly connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of LaunchDarkly configuration information gathered by following the instructions above
</Warning>

<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 **LaunchDarkly** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new LaunchDarkly connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

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

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

      <Step>
        Enter the configuration information from the previous section.
      </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 LaunchDarkly connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the LaunchDarkly connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    [Contact C1's support team](mailto:support@conductorone.com) to download the latest version of the connector.

    ### Step 1: Set up a new LaunchDarkly connector

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

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

      <Step>
        Choose how to set up the new LaunchDarkly connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

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

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your LaunchDarkly connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={null}
    # baton-launchdarkly-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-launchdarkly-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # LaunchDarkly config
      BATON_LAUNCHDARKLY_API_TOKEN: <LaunchDarkly API Access Token>

    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={null}
    # baton-launchdarkly.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-launchdarkly
      labels:
        app: baton-launchdarkly
    spec:
      selector:
        matchLabels:
          app: baton-launchdarkly
      template:
        metadata:
          labels:
            app: baton-launchdarkly
            baton: true
            baton-app: launchdarkly
        spec:
          containers:
          - name: baton-launchdarkly
            image: public.ecr.aws/conductorone/baton-launchdarkly:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-launchdarkly
            envFrom:
            - secretRef:
                name: baton-launchdarkly-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the launchdarkly connector to. launchdarkly data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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