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

# Enable GitLab Integration

> Connect your GitLab projects or groups to Sawmills so the Instrumentation Reviewer can analyze telemetry changes in merge requests via webhook.

## About GitLab Integration

The GitLab Integration connects your GitLab project or group to Sawmills Telemetry Reviewer.

After the integration is enabled, Sawmills can use the authorized GitLab access and webhook to support instrumentation review workflows.

See [Instrumentation Reviewer](/docs/sawmills-agent-instrumentation-reviewer).

## Step-by-Step: Configure GitLab Integration

### 1. Access Integrations

Open the user menu at the top right and select **Integrations**.

### 2. Start GitLab Setup

In the Integrations section, click **Connect GitLab**.

### 3. Enter Integration Details

Provide:

* **Integration name**
* **Scope type**: project or group
* **Scope path**

Use a full GitLab project path such as `group/project` for project-level setup.

### 4. Continue to GitLab

Click **Continue to GitLab** to start the authorization flow.

### 5. Authorize and Return

Authorize the connection in GitLab. After authorization completes, GitLab redirects you back to the Sawmills integrations page and Sawmills finishes creating the integration.

### 6. Verify the Integration

Confirm that the GitLab integration appears as connected for the selected project or group.

## What the Integration Is Used For

The GitLab integration is used by Sawmills Telemetry Reviewer to access repository code for instrumentation review workflows.

For GitLab, Sawmills creates a webhook for the selected project or group and stores the authorized access needed for reviewer operations.

## Requested GitLab Token Access

For GitLab, Sawmills Telemetry Reviewer needs:

* A token for the selected GitLab host
* Access to the selected **project** or **group**
* **Maintainer** access or higher on the relevant project scope
* A token that can call the GitLab API for both read and write operations

In practice, this means using a GitLab token with API access for the selected scope.

## Why This Access Is Needed

This access lets Telemetry Reviewer read merge request changes and repository context, publish review results back to GitLab, create the webhook used to trigger reviewer runs, and support note-driven commands such as rerun or cancel.