GitLab Server

Make your self-managed GitLab searchable in Glean

Indexes merge requests, code, issues, wikis, and epics from your self-managed GitLab instance for permission-aware search — so engineers find the code, reviews, and decisions they need without leaving Glean.

Version controlSelf-managedPersonal access tokenPermission-aware

Set up the connectorSee what gets indexed

At a glance

Authentication

Personal access token (PAT)

What it indexes

Merge requests, code, issues, wikis, epics

Permissions

GitLab permissions, enforced at query time

Network

Crawler must reach your instance (GCP and AWS)

Full crawl

Approximately every 28 days

Change updates

Near real-time via webhooks

General information

Overview

What the GitLab Server connector indexes, its permission model, and how crawling keeps content fresh.

Setup and configuration

Default

Setup

Choose an authentication path, create a personal access token, configure webhooks, and set up the connector in the Glean Admin console.

Requirements

The network access, credentials, and permissions you need before you begin.

Support

Troubleshooting and FAQs

Resolve setup, network, and content issues, and read answers to common questions.

Error codes

Look up connector error codes and what they mean.