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

# Install the GitLab Cloud integration for Qodo on-premises

> Install guide for Qodo automated code review on GitLab Cloud, for Qodo on-premises deployments.

export const onPrem_0 = true

export const showAllowlist_0 = undefined

<Note>
  This wizard can be used for Qodo multi-tenant, single-tenant, and on-premises deployments on GitLab Cloud (`gitlab.com`). For a self-hosted instance, see {onPrem_0 ? <a href="/on-prem/git-integration/install/gitlab">GitLab Server</a> : <a href="/install-qodo/gitlab/gitlab-server">GitLab Server</a>}.
</Note>

Qodo works directly with GitLab, using a dedicated GitLab service account with Developer-level permissions to post code review comments on merge requests. Qodo creates this account automatically using a personal access token you provide during setup, then discards the token.

You can configure Qodo for selected repositories or across your entire GitLab group. Configuration typically takes around 5–10 minutes.

Once installed, Qodo automatically processes merge requests and delivers actionable insights, such as code reviews, descriptions, and improvement suggestions, directly within your GitLab workflow.

## Prerequisites

Before you begin, ensure you have:

* Access to your Qodo portal.
* The Owner role on each top-level GitLab group you connect, needed for Qodo to create its service account in that group and set up webhooks.
* Network access from Qodo to `gitlab.com`.{showAllowlist_0 && <> If your GitLab groups use an IP allowlist, see <a href="/install-qodo/allowlist-qodo-outbound-ip-addresses">Allowlist Qodo's outbound IP addresses</a>.</>}{onPrem_0 && <> <code>gitlab.com</code> must also be able to reach your Qodo on-premises instance, to deliver webhooks.</>}

## Access the GitLab integration

<Steps>
  <Step>
    Log in to your Qodo portal.
  </Step>

  <Step>
    Start the installation wizard in one of the following ways:

    * **From the onboarding wizard**: If you're an organization admin signing in for the first time, the onboarding wizard opens automatically. In the Connect Git step, select **GitLab**. See [Set up Qodo with the onboarding wizard](/onboarding-wizard).
    * **From the homepage**: On the homepage, in the top right-hand side, click the **+** button next to Git providers. On the selection page, choose **GitLab**.
  </Step>
</Steps>

## Install Qodo on GitLab Cloud

<Steps>
  <Step title="Connect GitLab">
    <Frame>
      <img src="https://mintcdn.com/qodo/t2tb70f5WOSSF3zW/images/code-review/gitlab/gl-wizard-step-1-connect-gitlab.png?fit=max&auto=format&n=t2tb70f5WOSSF3zW&q=85&s=2f54af77cbc5d76ac2e1cfd7d7f8afcd" alt="GitLab wizard step 1, Connect GitLab, showing the GitLab URL and personal access token fields" width="1004" height="751" data-path="images/code-review/gitlab/gl-wizard-step-1-connect-gitlab.png" />
    </Frame>

    <Steps>
      <Step>
        Confirm the **GitLab URL** is `https://gitlab.com`. Sign in as a group Owner.
      </Step>

      <Step>
        Click **Create a token in GitLab** to open your GitLab access token settings directly.

        The `api` scope is required and preselected. Leave it selected when you create the token.

        <Note>
          This token is used once, to create the Qodo service account, and is never stored. You can set a short expiry, for example 1 day.
        </Note>
      </Step>

      <Step>
        Paste the token under **Your personal access token** and click **Next**.
      </Step>
    </Steps>
  </Step>

  <Step title="Select repositories">
    <Frame>
      <img src="https://mintcdn.com/qodo/t2tb70f5WOSSF3zW/images/code-review/gitlab/gl-wizard-step-2-select-repositories.png?fit=max&auto=format&n=t2tb70f5WOSSF3zW&q=85&s=0fd060e39476dbab26de9fc9835c255e" alt="GitLab wizard step 2, Select repositories, showing the group list with one group selected, the search bar, and Select all" width="1443" height="1090" data-path="images/code-review/gitlab/gl-wizard-step-2-select-repositories.png" />
    </Frame>

    <Steps>
      <Step>
        Find and select what to connect:

        * Use the search bar to find a specific group or repository, or browse the list of top-level groups you have access to.
        * Select a group to connect every repository within it, or drill into a group to select individual repositories.
        * Select **Select all** to connect everything you have access to in one step.

        <Note>
          On GitLab free-tier groups, which don't support group hooks, this step appears as "Select repositories" and Qodo creates a hook for each repository you select. On tiers with group hooks, it appears as "Select groups and repositories", and selecting a group creates a group hook.
        </Note>

        <Note>
          Repositories in personal namespaces aren't supported.
        </Note>
      </Step>

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

  <Step title="Verify connection">
    <Frame>
      <img src="https://mintcdn.com/qodo/rnnlQnSbpQSmCoXK/images/code-review/gitlab/gl-wizard-step-3-install-qodo.png?fit=max&auto=format&n=rnnlQnSbpQSmCoXK&q=85&s=e7dc53d8a16d1e3d3b7213db9ad38b7f" alt="GitLab wizard step 3, Verify connection, showing the confirmation banner and per-group connection status" width="999" height="793" data-path="images/code-review/gitlab/gl-wizard-step-3-install-qodo.png" />
    </Frame>

    Qodo confirms it's connected to your selected repositories and groups.

    * Each one shows its status: **Already connected** from a previous installation, or **Connected** if newly connected.
    * Installing across multiple top-level groups sets up each group as a separate installation, appearing as its own item on the [Installations tab](/governance/repositories/installations).
    * Click **Done**.
  </Step>
</Steps>

Qodo is now active on the repositories in the groups you selected. To connect more repositories under an existing installation, use [Manage the repositories in an installation](/governance/repositories/installations#manage-the-repositories-in-an-installation) on the Repositories page. To connect a different group, return to this wizard.

<Note>
  If you're connecting your Git provider as part of the onboarding wizard, the wizard continues to the next onboarding step once the connection completes. See [Set up Qodo with the onboarding wizard](/onboarding-wizard).
</Note>

## What happens after you connect

Qodo starts building context for your code reviews, and the following processes run automatically in the background:

* [Repository sync](/governance/repositories/installations#view-repository-sync-status-from-anywhere-in-the-portal): Syncs each connected repository with Qodo.
* [Pull request indexing](/governance/repositories/manage-repositories#check-repository-pr-history-indexing-status): Indexes each repository's pull request history.
* [Cross-repo discovery](/governance/repositories/relationships#view-cross-repo-discovery-status-from-anywhere-in-the-portal): Finds relationships between your repositories.

Track their progress from **Background activity** in the top-right corner of the portal.

<Tip>
  It's recommended to import your team's existing rules and skills, which lets Qodo enforce your coding standards in its reviews. See [Importing rules and skills](/governance/rule-enforcement/building-review-standards#importing-rules-and-skills).
</Tip>

## Verify the installation

<Steps>
  <Step>
    Open a new merge request in one of the connected repositories and confirm Qodo is triggered automatically.
  </Step>

  <Step>
    Add a comment using one of the supported commands:

    * `/agentic_describe`
    * `/agentic_review`

    Qodo should respond with a review or MR summary directly on the merge request.
  </Step>
</Steps>

## Troubleshooting

If Qodo doesn't respond on the merge request, check that GitLab can reach Qodo's webhook URL:

<Steps>
  <Step>
    In GitLab, navigate to the webhook settings of the connected group or repository.
  </Step>

  <Step>
    Copy the URL of the webhook Qodo created. The URL is different for each Qodo installation.
  </Step>

  <Step>
    Confirm that your network allows GitLab to reach that URL.
  </Step>
</Steps>

## Next steps

* [Repositories page](/governance/repositories): Manage which repositories Qodo is active on, or remove an installation.
* [Trigger a code review](/code-review/use-qodo-in-prs): Run a review automatically or on demand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.