---
title: "Gitlab Source Code Control"
slug: "git-lab-source-code-control"
updated: 2025-07-29T19:49:46Z
published: 2025-07-29T19:49:46Z
canonical: "docs.databee.buzz/git-lab-source-code-control"
---

> ## 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 Source Code Control

GitLab is an Open-Source code repository and collaborative software development platform for large DevOps and DevSecOps projects providing end-to-end DevOps capabilities for each stage of the software development lifecycle. More information can be found at [GitLab’s webpage.](https://about.gitlab.com/solutions/source-code-management/)

**Integration Method:** API

**Tables**: Group Management Class (3006), User access management class (3005), Ticket Inventory (99405001), Entity management class (3004)

List of events supported by this integration.

| **Events** | **Description** |
| --- | --- |
| Projects | Get a list of all visible projects across GitLab |
| Audit Events | Projects created/deleted, API tokens, users added/deleted |
| Members | Get list of members as part of organizational groups |
| Merge Requests | Get list of merge requests across in a project |

This integration supports the following versions.

| Gitlab Version Tested | GitLab Enterprise Edition 17.9.0-pre |
| --- | --- |
| Gitlab API version | v4.0 |

## Prerequisites

- User should have Admin access to the Gitlab for creating API tokens.
- User should have access to the DataBee console.

## Configuration Overview

1. Generate an API token on the GitLab console with the required scopes.
2. Add the [GitLab data feed](/user-manual/docs/git-lab-source-code-control#databee-configuration) integration in the DataBee console with the required API token.

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

## Gitlab Configuration

Start by creating an API Token for the integration.

1. Login to your GitLab account which has admin privileges. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-ic1vl02b.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
2. In the upper-left corner, select the avatar, then click **Preferences**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-yec7wmf2.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
3. Click the **Access tokens** side bar.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/Screenshot_GSCC_config_1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
4. Select “**Add new token**” under Personal access tokens. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-9mpmp7nc.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
5. Fill in a ‘Token name’, ‘Token description’ and ‘Expiration date’. Choose a 12-month expiration. Longer expiration times can minimize disruption. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-1s6tdx4q.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
6. Select the following scopes as highlighted below and click **Create personal access token**.
  - read_api
  - read_user
  - read_repository ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-e60263r1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
7. Copy and save the generated personal access token. This will not be available later to be copied. It is used when configuring DataBee. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-uo8byrhe.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)

## DataBee Configuration

To configure the data source,

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-source-code-control-image-b59kvnbo.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
2. Search for the **GitLab Source Code Control** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-xn46r8td.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-684wsxnv.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-uj4x2wxy.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
5. In the configuration page, confirm the following:
  - API Base URL: this is the base URL that DataBee will interact with
  - Authorization Method: Bearer Token
  - Token: paste the Personal Access Token generated earlier in the GitLab console.
  - Event types: preselected for all the events types the integration pulls. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/gitlab-source-code-control-image-tvbe4jqr.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A48%3A00Z&se=2026-10-30T13%3A48%3A00Z&sr=c&sp=r&sig=j%2BTH4iGkAegQD8GU4Bo0nyoiNDKieXZ3CkabvJuN9ag%3D)
6. 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 scopes/permissions are correct.

##