> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a GitLab connector

> C1 provides identity governance for GitLab. Integrate your GitLab instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

<Tip>
  **This is an updated and improved version of the GitLab integration!** If you're setting up a GitLab connector with C1 for the first time, you're in the right place.
</Tip>

## Capabilities

| Resource | Sync                                                          | Provision                                                     |
| :------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Projects | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

The GitLab connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning). Accounts will be created directly in self-hosted GitLab instances. If you're using GitLab.com, new accounts will generate an invitation email and will remain in a pending state until the invitation is accepted.

Information on last login is synced from self-hosted GitLab instances; this capability is not supported on GitLab.com due to permissions limitations.

## Gather GitLab credentials

Configuring the connector requires you to pass in credentials generated in GitLab. Gather these credentials before you move on.

<Warning>
  Any GitLab.com user can complete this task. If you're configuring self-hosted GitLab, a user with **admin** permissions in GitLab must perform this task.
</Warning>

### Create a personal access token

<Steps>
  <Step>
    In the GitLab menu bar, click your profile photo then click **Edit profile**.
  </Step>

  <Step>
    From the menu on the left side of the screen, click **Access tokens** then click **Add new token**.
  </Step>

  <Step>
    Give your token a name and set an expiration date.
  </Step>

  <Step>
    In the **Select scopes** area, select **api**.
  </Step>

  <Step>
    Click **Create personal access token**.
  </Step>

  <Step>
    Carefully copy and save the newly created token.
  </Step>
</Steps>

### Look up your GitLab group name

When new GitLab.com accounts are created, they must be assigned to a GitLab group. Look up the name of the group you want to add new accounts to.

<Steps>
  <Step>
    Navigate to **Menu** > **Groups** > **Your Groups**.
  </Step>

  <Step>
    Click on the group you wish to connect to C1.
  </Step>

  <Step>
    Make a note of the group name.
  </Step>
</Steps>

If you do not have any groups, follow the prompts to create a new group, and make a note of the name you choose.

**Done.** Next, move on to the connector configuration instructions.

## Configure the GitLab connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of GitLab credentials generated by following the instructions above
</Warning>

<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 **GitLab** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new GitLab connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Paste the token into the **Personal access token** field.
      </Step>

      <Step>
        Enter the GitLab group that newly created user accounts should be added to in the **Group** field.
      </Step>

      <Step>
        Enter `https://gitlab.com` or the self-hosted URL at which you access GitLab in the **URL** field.
      </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 GitLab connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the GitLab connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [GitHub repository](https://github.com/conductorone/baton-gitlab): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new GitLab connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new GitLab connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your GitLab connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-gitlab-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-gitlab-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # GitLab credentials if configuring with an access token
      BATON_TOKEN: <GitLab access token>
      BATON_ORGS: <Optional - list of GitLab orgs that you want to sync>

      # GitLab credentials if configuring with a GitLab app
      BATON_ACCESS_TOKEN: <GitLab access token>
      BATON_BASE_URL: <URL where you access GitLab (default is "https://gitlab.com/")>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true
      BATON_ACCOUNT_CREATION_GROUP: <GitLab group that newly provisioned accounts will be added to>
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-gitlab.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-gitlab
      labels:
        app: baton-gitlab
    spec:
      selector:
        matchLabels:
          app: baton-gitlab
      template:
        metadata:
          labels:
            app: baton-gitlab
            baton: true
            baton-app: gitlab
        spec:
          containers:
          - name: baton-gitlab
            image: ghcr.io/conductorone/baton-gitlab:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-gitlab
            envFrom:
            - secretRef:
                name: baton-gitlab-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the GitLab connector to. GitLab data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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