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

# Set up a KnowBe4 connector

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

C1 provides identity governance for KnowBe4. Integrate your KnowBe4 instance
with C1 for unified visibility and governance over group membership.

## Capabilities

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

This connector is **read-only**: it syncs users, groups, and group memberships
through the KnowBe4 Reporting API v1 and does not provision changes back to
KnowBe4.

## Gather KnowBe4 credentials

<Warning>
  You need a KnowBe4 account with permission to manage API access in the KnowBe4
  console.
</Warning>

<Steps>
  <Step>
    Sign in to the KnowBe4 console and open **Account Settings** > **API**.
  </Step>

  <Step>
    Enable the **Reporting API** and create an API key. Copy the key — it is the
    bearer token the connector uses.
  </Step>

  <Step>
    Note your KnowBe4 region. The Reporting API base URL is
    `https://us.api.knowbe4.com/v1` (US) or `https://eu.api.knowbe4.com/v1`
    (EU). Using the wrong region returns authorization errors or empty results.
  </Step>
</Steps>

## Configure the KnowBe4 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 **KnowBe4** 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 KnowBe4 credentials:

        * **Base URL**: your regional Reporting API URL, for example `https://us.api.knowbe4.com/v1`.
        * **API token**: the Reporting API key from the KnowBe4 console.
      </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 KnowBe4 connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector with your regional base URL and the API token
        secret.
      </Step>

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

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