> ## 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 Langfuse connector

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

C1 provides identity governance for Langfuse. Integrate your Langfuse
organization with C1 for unified visibility and governance over who can
access your organization and its projects.

## Capabilities

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

The connector syncs your Langfuse users (via the SCIM 2.0 directory), your
organization, and every project, along with each member's role
(**Owner**, **Admin**, **Member**, or **Viewer**) at both the organization
and project level.

## Gather Langfuse credentials

<Warning>
  You need an **Owner** or **Admin** on the Langfuse organization to create
  organization-scoped API keys. Project-scoped keys do **not** work — the
  connector requires organization-scoped keys.
</Warning>

<Steps>
  <Step>
    Sign in to Langfuse and open **Organization Settings** for the
    organization you want to connect.
  </Step>

  <Step>
    Go to **API Keys** and create a new **organization-scoped** key pair.
    Langfuse shows the **Public Key** and the **Secret Key** once — copy
    both. (If you only see project-scoped keys, switch to the organization
    settings; project keys are rejected by the connector.)
  </Step>

  <Step>
    Note your Langfuse region so you can supply the matching base URL:

    * **EU** (default): `https://cloud.langfuse.com`
    * **US**: `https://us.cloud.langfuse.com`
    * **JP / HIPAA / self-hosted**: use the origin of your deployment.
  </Step>
</Steps>

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

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

        * **Langfuse Base URL**: The origin for your region, without a
          trailing slash (for example, `https://cloud.langfuse.com`).
        * **Langfuse Public Key**: The organization-scoped public key.
        * **Langfuse Secret Key**: The organization-scoped secret key.
      </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 Langfuse connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the Langfuse organization-scoped key pair.
      </Step>

      <Step>
        Configure the connector with:

        * **Langfuse Base URL**: The origin for your region, without a
          trailing slash.
        * **Langfuse Public Key**: The organization-scoped public key.
        * **Langfuse Secret Key**: The organization-scoped secret key.
      </Step>

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

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