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

# Connect GitLab to Canvas

> Connect your GitLab.com account so the Canvas Agent can read merge requests, commits, pipelines, job logs, and issues during an investigation.

Connect your GitLab.com account to let the Canvas Agent read the code changes and pipelines behind an incident during an investigation.

> [!TIP]
>
> Connectors work per user and per Honeycomb Team.
> You connect your own account, and the Canvas Agent uses the connected service as your account.
> Connecting a connector does not connect it for anyone else on your Honeycomb Team.
> If you belong to more than one Honeycomb Team, connect your account in each Team.
> Your [tool permissions](https://docs.honeycomb.io/investigate/canvas/connectors/#managing-tool-permissions) also apply only to you, in one Honeycomb Team.
> There are no Team-level connector controls yet.
>
> Connectors work through your account, so an [automatic investigation](https://docs.honeycomb.io/investigate/canvas/auto-investigate.md) has no connector access at all.

## What the Canvas Agent can do

* Read projects, repository files, branches, tags, commits, and releases.
* Read merge requests, pipelines, jobs, and job artifacts.
* Search code, work items, and labels.
* Comment on, review, create, or update merge requests.
* Create a branch, or commit files to a branch.
* Run, retry, or cancel a pipeline.
* Create or update work items.
* Merge a merge request.

> [!NOTE]
>
> Honeycomb reviews each tool in a connector and gives it a default permission.
> Until you set your own tool permissions, these defaults apply:
>
> * The Canvas Agent runs reviewed read-only tools without asking.
> * For reviewed write tools and destructive tools, the Canvas Agent asks you to approve each call.
> * The Canvas Agent does not run deprecated tools.
>
> The Canvas Agent runs a tool only when your investigation needs it.
> To change the defaults, visit [Managing tool permissions](https://docs.honeycomb.io/investigate/canvas/connectors/#managing-tool-permissions).

## Access this connector grants

> [!WARNING]
>
> The Canvas Agent authenticates to GitLab with your identity.
> It can read every project that your GitLab account can see.
> If you approve a commit, the Canvas Agent can commit to any branch that you can push to, including the default branch.
> If you approve a merge, the merge can put code on a protected branch.
> If you approve a pipeline run, the pipeline can deploy.
> Honeycomb classifies the commit and merge tools as destructive tools, so the Canvas Agent asks you to approve each call by default.

## Before you connect

The Canvas Agent connects to GitLab through the GitLab MCP server.
The server has these requirements:

* Your projects must be on GitLab.com.
  GitLab Self-Managed is not supported.
* An owner of your top-level GitLab group must allow MCP server access.
* Some tools, such as the vulnerability and GitLab Duo tools, need GitLab Ultimate, the GitLab Duo Agent Platform, or a GitLab toolset that you turn on.

## Connecting GitLab

1. Navigate to  **Canvas** > **Connectors**.
2. Find **GitLab** in the connector list.
3. Select **Connect**.
4. Authorize Honeycomb from the GitLab authorization page.

After the connection succeeds, the GitLab connector shows a **Connected** badge.

## Turning GitLab on or off

1. In a Canvas chat, select the  plus (`+`) button.
2. Choose **Connectors**.
3. Use the toggle beside **GitLab**.

## Disconnecting GitLab

1. Navigate to  **Canvas** > **Connectors**.
2. Find **GitLab** and select **Manage**.
3. Select **Disconnect**.

To learn more, visit [Canvas Connectors](https://docs.honeycomb.io/investigate/canvas/connectors/).