GitLab

Last updated: September 2026

Connect GitLab Cloud or GitLab Self-Managed to sync repository, pull request, and contributor activity into GitKraken Insights. Your git provider powers every PR, commit, contributor, and cycle-time metric.

Before you start: make sure you have the right access. See the prerequisites table on the Connect Your Data overview.

GitLab

Connect GitLab to pull activity for your GitLab groups. It connects with a personal access token carrying the read_api scope.

1. In Data Connections, click + next to GitLab.
2. Optionally name the connection, then create the token — the modal’s Create a token link opens GitLab’s token form for you.
3. Paste the GitLab personal access token and click Validate, then Connect.

GitLab personal access tokens start with glpat-…. The connection only sees the groups and projects the token’s account can access.

GitLab Self-Managed

Connect GitLab Self-Managed to sync activity from a GitLab instance you run yourself.

Requirements:

• The server must be reachable from GitKraken over https with a publicly-trusted certificate.
• A personal access token with the read_api scope.

1. In Data Connections, click + next to GitLab Self-Managed.
2. Optionally name the connection, then enter the Server URL — for example https://gitlab.yourcompany.com.
3. Paste the GitLab personal access token and click Validate, then Connect.

As with GitLab cloud, the connection only sees the groups and projects the token’s account can access.

Troubleshooting

For general connection troubleshooting, see Troubleshooting setup on the Connect Your Data overview.

After connecting

Once your connection is active, continue with the remaining setup steps on the Connect Your Data overview:

• Set your benchmarks
• Map developer identities
• Invite your team