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

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

C1 provides identity governance for Guru. Integrate your Guru team 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" /> |           |

## Gather Guru credentials

<Warning>
  The connector authenticates as a Guru user with HTTP Basic auth. The user whose
  token you use must be able to read the team's members and groups. A user with an
  administrative role on the team is the safest choice.
</Warning>

<Steps>
  <Step>
    Sign in to Guru with the account you want the connector to use.
  </Step>

  <Step>
    Create an API token for that account from your Guru API settings. Note the
    account's email address — it is the username half of the credential.
  </Step>

  <Step>
    Copy the token value. You provide the account email as **User Email** and
    the token as **API Token** when configuring the connector.
  </Step>
</Steps>

## Configuration fields

| Field        | Required | Description                                                                                                          |
| ------------ | -------- | -------------------------------------------------------------------------------------------------------------------- |
| `user-email` | Yes      | The email address of the Guru user whose token authenticates requests. Sent as the username half of HTTP Basic auth. |
| `api-token`  | Yes      | That user's Guru API token. Sent as the password half of HTTP Basic auth.                                            |

## Synced resource types

* **Users**: Guru members from `/members`. A member whose status is not active
  is synced as disabled.
* **Groups**: Guru groups from `/groups/usergroups`, each with a `member`
  entitlement.
* **Group memberships**: membership assignments from
  `/groups/{group_id}/members`.

## Special notes

* Provisioning is not supported in the current build; the connector performs
  read calls only.
* The connector authenticates with HTTP Basic auth using the user email and API
  token.

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

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

        * **User Email**: The email address of the Guru user whose token you are using.
        * **API Token**: That user's Guru API token.
      </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 Guru connector is now pulling access data into C1.
  </Tab>

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

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

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

      <Step>
        Choose how to set up the new Guru connector, set the owner, and click **Next**.
      </Step>

      <Step>
        In the **Settings** area, click **Edit**, then click **Rotate** to
        generate a new Client ID and Client Secret. Store these values securely
        for your deployment.
      </Step>

      <Step>
        Configure C1 credentials and Guru credentials as environment variables:

        ```bash theme={"theme":{"light":"css-variables","dark":"css-variables"}}
        BATON_CLIENT_ID=<C1 client ID>
        BATON_CLIENT_SECRET=<C1 client secret>
        BATON_HOST_ID=baton-guru
        BATON_USER_EMAIL=<Guru user email>
        BATON_API_TOKEN=<Guru API token>
        ```
      </Step>

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

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