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

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

C1 provides identity governance for GitBook. Integrate your GitBook
organization with C1 for unified visibility and governance over user access.

## Capabilities

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

## Gather GitBook credentials

<Warning>
  Use a token from a user that can see the organization's members and teams.
  The token inherits the access of the user that created it, and one connector
  reads a single organization.
</Warning>

<Steps>
  <Step>
    In GitBook, open your user account's developer settings and create a
    personal access token.
  </Step>

  <Step>
    Copy the token. GitBook shows it once at creation time.
  </Step>

  <Step>
    Note the unique identifier of the organization you want to read. You can
    find it in the organization's settings page URL in GitBook, or list the
    organizations your token can see with
    `GET https://api.gitbook.com/v1/orgs`.
  </Step>
</Steps>

## Configuration fields

| Field             | Required | Description                                                                                                               |
| ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------- |
| `base-url`        | Yes      | The GitBook API host, with no path and no trailing slash. For GitBook's hosted product this is `https://api.gitbook.com`. |
| `organization-id` | Yes      | The unique identifier of the GitBook organization to read. One connector reads one organization.                          |
| `api-key`         | Yes      | A GitBook personal access token from your user account's developer settings.                                              |

## Synced resource types

* **Users**: organization members from `/v1/orgs/{organization_id}/members`,
  including guests and SSO-provisioned users. Disabled members sync with a
  disabled status.
* **Teams**: organization teams from `/v1/orgs/{organization_id}/teams`, each
  with a `member` entitlement.
* **Team membership**: team-member grants from
  `/v1/orgs/{organization_id}/teams/{team_id}/members`. Team owners and
  members both hold the `member` entitlement.

## Special notes

* Provisioning is not supported in the current build.
* The connector authenticates with the personal access token as a bearer
  credential.
* One connector reads the single organization named by `organization-id`.
  Spaces, sites, and collections are content surfaces and are not synced.

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

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

        * **GitBook API host**: The API host, usually `https://api.gitbook.com`.
        * **Organization ID**: The unique identifier of the organization to read.
        * **API token**: The personal access 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 GitBook connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the GitBook credentials.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_BASE\_URL**: The API host, usually `https://api.gitbook.com`.
        * **BATON\_ORGANIZATION\_ID**: The unique identifier of the organization to read.
        * **BATON\_API\_KEY**: The personal access token.
      </Step>

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

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