Skip to content
Integrations/GitLab/Connection Guide
Connection Guide

Connect GitLab Without Breaking the Audit Trail

Use this guide to connect GitLab or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategorySource control
Checklist2 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect GitLab and make sure the first collection lands cleanly.

  1. 1
    Create GitLab token with read scopes.
  2. 2
    Validate by listing projects.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

token_or_client

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

read_apiread_userread_repository