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

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

C1 provides identity governance for GitGuardian. Integrate your
GitGuardian workspace with C1 for unified visibility and governance over
user access.

## Capabilities

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

The connector reads one GitGuardian workspace. It syncs the workspace's
members and teams, along with each team's membership — including whether
each member is a team leader or a regular team member. Each member's
workspace access level (owner, manager, member, or restricted) and
active status are carried on the member for visibility, and deactivated
members appear as disabled users.

## Gather GitGuardian credentials

<Warning>
  You need a manager or owner access level on your GitGuardian workspace to
  create an API token with the required scopes.
</Warning>

<Steps>
  <Step>
    Sign in to the GitGuardian dashboard.
  </Step>

  <Step>
    Go to **API** > **Personal access tokens** and click
    **Create token**.
  </Step>

  <Step>
    Give the token a descriptive name, such as `ConductorOne`, and
    select the **members:read** and **teams:read** scopes.
  </Step>

  <Step>
    Copy the token when it is shown.
  </Step>
</Steps>

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

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

        * **API token**: the token created in the API settings.
      </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 GitGuardian connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the GitGuardian API token.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_GITGUARDIAN\_API\_TOKEN**: the token created in the API
          settings.
      </Step>

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

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