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
Teams

Gather GitBook credentials

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.

1. In GitBook, open your user account’s developer settings and create a personal access token.

2. Copy the token. GitBook shows it once at creation time.

3. 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.

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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for GitBook and click Add.

3. 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.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. 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.
9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your GitBook connector is now pulling access data into C1.

Self-hosted

Follow these instructions to run the GitBook connector in your own environment.

1. Create secrets for the GitBook credentials.

2. 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.
3. Deploy the connector using your standard self-hosted connector process.

Done. Your GitBook connector is now pulling access data into C1.