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

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

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

## Capabilities

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

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

<Warning>
  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.
</Warning>

<Steps>
  <Step>
    Sign in to your Gitea instance as a site administrator.
  </Step>

  <Step>
    Go to **Settings** > **Applications** > **Manage Access Tokens**.
  </Step>

  <Step>
    Generate a new token and grant it the `read:admin`, `read:organization`,
    and `read:user` scopes.
  </Step>

  <Step>
    Copy the generated token and note your instance base URL (for example,
    `https://gitea.example.com`).
  </Step>
</Steps>

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

      <Step>
        Choose how to set up the new Gitea 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 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.
      </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 Gitea connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the Gitea credentials.
      </Step>

      <Step>
        Configure the connector with:

        * **Gitea Base URL**: The origin of your Gitea instance, 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 (default 50).
      </Step>

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

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