/ /

GitLab connector- Overview

Updated 39 seconds ago

Introduction

The GitLab connector allows Simpplr Enterprise Search to index your GitLab engineering content, making it easily discoverable and searchable directly within Simpplr, alongside all other configured sources.

GitLab is a source code management and DevOps platform used for code reviews, issue tracking, and project documentation. With this connector, you can:

  • Search merge requests, issues, and project wikis from GitLab alongside intranet and other connectors.

  • Search GitLab with permissions enforced — results are filtered to content the signed-in user already has access to in GitLab.

  • Search results and AI-generated summaries from GitLab appear alongside all other connected sources in Simpplr.

Capabilities at a glance

Capability

Description

What it indexes

Merge requests, issues, wikis

Authentication

Personal Access Token (PAT)

Access level

Read-only — the connector never modifies content in GitLab

Enforced permissions

Identity-aware, enforced at query time. Syncs users and effective project memberships.

Credential scope

read_api + read_repository + read_user

Audiences

Connector can be enabled or disabled for specific audiences within Simpplr.

Supported editions

GitLab Enterprise only (GitLab.com SaaS or self-managed). User email addresses are required for permission sync and are only available through the GitLab API on Enterprise accounts.

Sync schedule

Incremental sync: every hour · Full sync: every week

Filters

Content date (default: last 2 years), object type (issues, merge requests, wikis)

Content types

Type

Supported

Details

Merge requests

Yes

Title, description, status, and branch metadata indexed

Issues

Yes

Title, description, labels, status, and assignee metadata indexed

Wikis

Yes

Wiki page title and content indexed

For fields synced per content type and how each appears in search results, see Content, Sync & Limitations - GitLab.

Filters

Filter

Description

Content date

Applies to: Merge requests, issues · Enabled by default: Yes (created or updated in the last 2 years)

Object type

Applies to: All content · Enabled by default: Yes (issues, merge requests, and wikis)

Known limitations

  • GitLab APIs do not expose deletions incrementally, so deleted merge requests and issues are removed from search during the next full sync.

  • Attachments, source code files, commits, and CI/CD pipeline data are not indexed.

  • A GitLab Enterprise account is required. Non-Enterprise editions do not expose user email addresses through the API, so permission sync cannot resolve identities.

For full detail on each limitation, see Content, Sync & Limitations - GitLab.

Related pages

Page

What it covers

Permissions & Security - GitLab

Auth mechanism, credential scope, permission design, propagation latency, supported editions

Setup - GitLab

Prerequisites and step-by-step configuration

Content, Sync & Limitations - GitLab

Fields synced per content type, sync schedules, data freshness, limitations in detail

Troubleshooting & FAQs - GitLab

Connector-specific issues and FAQs

Was this article helpful?
Subscribe to receive updates on this article