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
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
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your GitGuardian connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for GitGuardian 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 GitGuardian credentials:
- API token: the token created in the API settings.
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.