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

​
Capabilities

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

You need a manager or owner access level on your GitGuardian workspace to create an API token with the required scopes.
1
Sign in to the GitGuardian dashboard.
2
Go to API > Personal access tokens and click Create token.
3
Give the token a descriptive name, such as ConductorOne, and select the members:read and teams:read scopes.
4
Copy the token when it is shown.

​
Configure the GitGuardian connector

Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Integrations > Connectors and click Add connector.
2
Search for GitGuardian and click Add.
3
Choose how to set up the new GitGuardian connector.
4
Set the owner for this connector.
5
Click Next.
6
Find the Settings area of the page and click Edit.
7
Enter the GitGuardian credentials:
  • API token: the token created in the API settings.
8
Click Save.
9
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your GitGuardian connector is now pulling access data into C1.