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

​
Capabilities

The connector syncs users, organizations, and teams. It maps organization membership and team membership as access grants, records each team’s access level (none, read, write, admin, or owner), and surfaces a user’s instance-level administrator flag as a user attribute.

​
Gather Gitea credentials

The connector reads the Gitea admin APIs for users and organizations, so the access token must belong to a site administrator with the read:admin scope. A token without site-admin rights cannot list users or organizations.
1
Sign in to your Gitea instance as a site administrator.
2
Go to Settings > Applications > Manage Access Tokens.
3
Generate a new token and grant it the read:admin, read:organization, and read:user scopes.
4
Copy the generated token and note your instance base URL (for example, https://gitea.example.com).

​
Configure the Gitea 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 Gitea and click Add.
3
Choose how to set up the new Gitea 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 Gitea credentials:
  • Gitea Base URL: The origin of your Gitea instance, with no trailing slash, for example https://gitea.example.com.
  • Gitea API Token: A site-administrator personal access token.
  • Page Size (optional): Match this to your instance’s MAX_RESPONSE_ITEMS setting. The default is 50; leave it blank unless your instance uses a different value.
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 Gitea connector is now pulling access data into C1.