---
title: "Gitlab Compliance Center"
slug: "gitlab-compliance-center"
updated: 2026-10-26T14:42:58Z
published: 2026-10-26T14:42:58Z
canonical: "docs.databee.buzz/gitlab-compliance-center"
---

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

# Gitlab Compliance Center

GitLab is a comprehensive DevSecOps platform that manages the entire software development lifecycle (SDLC). It provides Git repository management, continuous integration/continuous deployment (CI/CD), code review, issue tracking, within a single platform.

More information can be found [Gitlab's Website](https://about.gitlab.com/).

**Integration Method:** API

**Tables**: Detection Finding (2004)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Compliance Violations | Detect compliance violations in merge requests. |

This integration supports the following versions.

|  |  |
| --- | --- |
| Gitlab Version | 18.0 |

> **Note:**
> 
> Gitlab’s Graphql is versionless. More information can be found [here](https://docs.gitlab.com/api/graphql/#breaking-changes).

## Prerequisites

- The user should have access to [GitLab](https://gitlab.com/users/sign_in) with an account that has the **Administrator** privileges.
- The user should have access to the DataBee console.

> **Test Connection**
> 
> The GitLab Compliance Center integration supports the **Test Connection** button in the DataBee feed configuration. Use this to validate that DataBee can successfully reach the GitLab Compliance Center API with the credentials you have provided before saving the feed configuration.

## Configuration Overview

1. Generate an API token with the required scopes.
2. Add the [Gitlab Compliance Center](/docs/gitlab-compliance-center#Databee_Config) in the DataBee console with the below parameters.

| **DataBee Parameter** | **Gitlab Parameter** |
| --- | --- |
| Token | Personal Access Token |

## Gitlab Compliance Center Configuration

1. Login to the Gitlab portal and on the left sidebar, select your **avatar**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-811ga7k9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
2. Select **Edit Profile**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-hgczsdug.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
3. On the left sidebar, select **Access tokens**. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-3hdlfqnf.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
4. Under Personal access tokens, click on **Add new token**. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-zg6k6et5.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
5. Enter a ‘Token name’, select the token ‘Expiration date’ and check the **read_api** scope. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-4vswdxa3.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
6. Scroll down and click on **Create personal access token**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-4y9rujsu.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
7. Copy the token and save it somewhere safely. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-au6d3tb0.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)

> Note:
> 
> After you leave the page, you no longer have access to the token.

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-sdooo18t.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
2. Search for the **Gitlab Compliance Center** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-le4fpebx.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-nadu11m4.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-jkdt95mz.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
5. In the configuration page, confirm the following:
6. API Base URL: this is the base URL that DataBee will interact with.
7. Authorization Method: Bearer Token
8. Token: paste the Personal Access Token generated earlier in the GitLab console.
9. Event Types: preselected for all the event types that integration pulls. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-compliance-center-may2025-image-2d9uczdd.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A00%3A45Z&se=2026-10-30T13%3A00%3A45Z&sr=c&sp=r&sig=gDe%2Ft%2F7cyrYo0vGMi5ObWxlMMP7VuARchcDVJMFGseo%3D)
10. Click **Submit.**

## Troubleshooting Tips

- Ensure the token is pasted correctly. Since you cannot view the token after the 1st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
- Ensure the Gitlab Compliance Center scopes/permissions are correct.