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

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

C1 provides identity governance for Codacy. Integrate your Codacy organization
with C1 for unified visibility and governance over user access.

## Capabilities

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

The connector syncs the people of your Codacy organization as user identities.
Each user carries their name, email, and Git-provider username, so you can see
who has access to your organization on Codacy.

## Gather Codacy credentials

<Warning>
  You need a Codacy **account API token** for an account that is a member of the
  organization you want to sync. The token grants access to your Codacy account,
  so treat it as a secret.
</Warning>

<Steps>
  <Step>
    Sign in to Codacy as a member of the organization you want to sync.
  </Step>

  <Step>
    Open your account settings and go to **Access management** → **API tokens**.
  </Step>

  <Step>
    Create a new **account API token** (not a project API token). Copy the
    generated token — you will use it to configure the connector.
  </Step>

  <Step>
    Note the **Git provider** that hosts your organization (GitHub, GitLab, or
    Bitbucket) and the **organization name** as it appears on that provider.
  </Step>
</Steps>

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

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

        * **API token**: The account API token you created in Codacy.
        * **Git provider**: Your provider's Codacy code — `gh` for GitHub, `gl` for GitLab, or `bb` for Bitbucket.
        * **Organization name**: Your organization's name on the Git provider.
      </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 Codacy connector is now pulling access data into C1.
  </Tab>

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

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

      <Step>
        Configure the connector environment variables:

        * **BATON\_CODACY\_API\_TOKEN**: The account API token (store this as a secret).
        * **BATON\_CODACY\_PROVIDER**: Your provider's Codacy code (`gh`, `gl`, or `bb`).
        * **BATON\_CODACY\_ORGANIZATION**: Your organization's name on the Git provider.
      </Step>

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

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