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

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

C1 provides identity governance for Crisp. Integrate your Crisp website with
C1 for unified visibility and governance over the operators who can access your
customer conversations.

## Capabilities

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

The connector syncs the operators of a single Crisp website along with the
website itself, and the membership graph that grants each operator their role
on the website. Crisp roles map to two entitlements on the website: **owner**
and **member**.

<Note>
  Operators are the members of your Crisp team (the agents who handle
  conversations), not your end customers. Each operator holds either the owner or
  member role on the website.
</Note>

## Gather Crisp credentials

<Warning>
  Generate the API token from an operator with the **owner** role on the website.
  A token with insufficient access cannot list the website's operators, and the
  sync fails.
</Warning>

Crisp authenticates the REST API with a token pair — an **identifier** and a
**key** — together with the **website ID** you want to govern.

<Steps>
  <Step>
    Sign in to the [Crisp Marketplace](https://marketplace.crisp.chat/) as an
    owner of the website.
  </Step>

  <Step>
    Create a token pair for the REST API. Copy both the **identifier** and the
    **key**. The key is shown only once.
  </Step>

  <Step>
    Open your website in the Crisp dashboard and copy the **Website ID** from
    the dashboard URL (`app.crisp.chat/website/<WEBSITE-ID>/`) or from website
    settings.
  </Step>
</Steps>

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

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

        * **Crisp API identifier**: The identifier half of your token pair.
        * **Crisp API key**: The key half of your token pair.
        * **Crisp Website ID**: The website you want to govern.
        * **Crisp API tier** (optional): The tier of your token pair —
          `plugin`, `website`, or `user`. Leave blank to use `plugin`.
      </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 Crisp connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector with:

        * **Crisp API identifier**: The identifier half of your token pair.
        * **Crisp API key**: The key half of your token pair, supplied as a
          secret.
        * **Crisp Website ID**: The website you want to govern.
        * **Crisp API tier** (optional): The tier of your token pair —
          `plugin`, `website`, or `user`. Defaults to `plugin`.
      </Step>

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

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