Skip to main content
Connectors

Connecting GitLab

Authorize GitLab, choose client-approved projects, and bring read-only commit, merge-request and issue summaries into the relevant claim project.

ReviewedAugust 22, 2026

ForClient portal users and claim preparers

Find itClient portal → Connect; consultant Client → Collaboration

The GitLab connector retrieves summarized activity only from projects the client approves. The client can authorize with OAuth or a personal access token, and the credential is encrypted at rest.

Connect approved projects

  1. The client signs in to their SREDlog portal, opens Connect, and chooses GitLab.
  2. Authorize with GitLab OAuth. If a provider administrator requires a token, open Advanced and use a narrowly scoped, expiring read-only access token.
  3. After returning to SREDlog, choose Share Projects, select the projects the consultant may access, and save the shared-access list.
  4. The consultant opens the client's Collaboration tab, opens Projects, maps each approved project, sets the activity window, and chooses Save & sync.

What enters SREDlog

SREDlog retrieves commit messages, timestamps, authorship, merge-request activity, and issue activity. It does not store source-code contents, write to GitLab, or inspect unapproved projects.

Disconnect or troubleshoot

If a project is missing, confirm the authorizing account can read it and that the client saved it under Share Projects. Use Sync in the consultant's Connected sources panel to refresh evidence. Disconnect in SREDlog and revoke the provider grant or token to stop access.

See the GitLab setup steps and data boundary.

Was this helpful?

Tell us what was missing and we’ll improve this guide.

Send feedback