> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/managed-analysis/gitlab-installation.md).
# GitLab Installation
{% hint style="info" %}
The GitLab integration is unified for both Cloud and Self-Managed plans. If you’re using a Self-Managed instance, you’ll simply be prompted to enter your instance URL.
Note that GitLab **Group Access Tokens** aren’t available on the Cloud Free tier per GitLab policy.
Additionally, the GitLab integration does not yet support GitLab Dependency Scanning.
{% endhint %}
Integrating Konvu with GitLab provides the following benefits:
* List your repositories
* Analyze your code to figure out your stack (frontend/backend, frameworks, OS, web servers, etc.)
* Your connected SCA integrations are automatically matched to your GitLab repositories to triage their exploitability using Konvu's [source code analysis](/konvu/get-started/connect-your-environment/source-code.md). They are imported once a day.
## Install GitLab Integration
{% hint style="info" %}
The GitLab integration relies on **Group Access Tokens,** and Konvu handles all token rotation. Just enter your token once and no further action will be required.
Information on **Group Access Tokens** can be found [here](https://docs.gitlab.com/ee/user/group/settings/group_access_tokens.html)
{% endhint %}
1. Sign in to Konvu
2. Click **Integrations**
3. Under "Add A New Integration" click on GitLab
4. If you are on a Self-Managed plan, hit the "*I'm using an on-premise GitLab instance"* button and enter your instance URL
5. Navigate to your Access Tokens page in GitLab, create a token with the required permissions and role, and copy it
6. Paste the token into Konvu where prompted
## Permissions & Roles Required
Permissions and roles are embedded in the **Group Access Token** you supply. The integration depends on a minimum required set for the integration to be successful.
| Permissions | Use Case |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| self\_rotate |
Allows Konvu to automatically refresh your Group Access Token before it expires.
Konvu immediately self-rotates the token during integration setup, which provides the necessary control to monitor its lifecycle and rotate it proactively.
|
| read\_api | Default permission to read groups & projects metadata |
| read\_repository | Read repository files, commits, and branches |
| Roles | Use Case |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Reporter or higher |
Required to allow Konvu to clone your repositories and access your code to analyze its structure and identify your tech stack, allowing Konvu to filter out irrelevant vulnerabilities.
Konvu does not store your code. Only minimal stack metadata. Your code stays secure, with privacy as our priority. Read more.
|
## Uninstall GitLab Integration
You can remove the GitLab integration by removing it from the **Integrations** page on Konvu directly.
You can also revoke the **Group Access Token** from your GitLab instance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.konvu.com/konvu/get-started/connect-your-environment/source-code/managed-analysis/gitlab-installation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
