Issues & support
Set up GitLab (issues & MRs)
Connect GitLab to make the issues and merge requests in your projects searchable — each becomes a document with its description and note thread, tied to its project, author and labels. Works with gitlab.com and self-hosted. Read-only.
Before you start
- GitLab → your avatar → Preferences → Access tokens, and add a new token with the read_api scope.
- A project or group access token (created under that project/group's Settings → Access Tokens) also works and isn't tied to a person.
- Copy it right away — GitLab shows it once.
- Documents → GitLab, paste the token as Access token; set GitLab URL if self-hosted (blank means gitlab.com — the token must come from the same server).
- Projects: list group/project paths (sub-groups included, e.g. group/team/project) or numeric project ids, one per line — blank syncs every project the token's account is a member of.
- Include: issues and merge requests, issues only, or merge requests only.
- State: open and closed, or open only.
- Choose access groups, Test, then Sync.
What comes in
- Each issue and merge request becomes a document: title, description and its note thread, tied to its project, author, assignees and labels.
- Each project also becomes a concept card.
Access
Confidential issues follow the project's own members: GitLab's Reporter role and above become viewers of that issue, re-checked as the source syncs. Everything else — regular issues, merge requests — is visible to whoever this source's access groups grant. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
A confidential issue whose member emails can't be resolved falls back to this source's access groups rather than going invisible. Read-only: only the read_api scope is used.
Last updated 20 Sep 2026