Skip to content
Overvy Docs

Connecting GitLab

Overvy connects to GitLab using a personal access token (PAT). This works with GitLab.com and self-hosted GitLab instances.

Create an access token

Section titled “Create an access token”
  1. In GitLab, go to Settings > Access Tokens (user, group, or project level).
  2. Create a new token with the api scope.
  3. Copy the token (it starts with glpat-).

Connect to Overvy

Section titled “Connect to Overvy”
  1. Go to Settings > Integrations in Overvy.
  2. Expand Add GitLab Connection.
  3. Fill in:
    • Group or username: the namespace path (e.g. my-org, my-org/sub-group, or your username)
    • Access token: paste your glpat- token
    • Instance URL: leave blank for GitLab.com, or enter your self-hosted URL (e.g. https://gitlab.example.com)
  4. Click Connect.

Register webhooks

Section titled “Register webhooks”

After connecting, click Register webhooks on the connection to enable automatic sync. Without webhooks, you need to sync manually from the backlog page.

Manage the connection

Section titled “Manage the connection”
  • Assigned/Unassigned toggle: assign the connection to include its issues in the current workspace.
  • Remove: disconnect the GitLab connection entirely.

How sync works

Section titled “How sync works”

Like GitHub, GitLab issues sync via manual sync and webhooks. Webhooks keep the board current when issues change on GitLab.

Security

Section titled “Security”

Your GitLab access token is encrypted at rest using AES-256-GCM before it is stored. Overvy decrypts it only when making API calls to GitLab on your behalf.