> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/get-started/onboarding-to-ox/source-control/gitlab-1.md).

# GitLab

GitLab is a complete DevOps platform that provides source code management, CI/CD pipelines, security testing, package registries, and collaboration capabilities in a single application.

Connecting GitLab to OX enables OX to discover repositories, analyze source code, scan open source dependencies, monitor security posture, and correlate findings across your software development lifecycle.

### What OX adds

* **Context and correlation:** OX maps GitLab findings to applications, services, and teams to show impact and ownership.
* **Prioritization with severity factors:** OX may reprioritize scanner severities when exploitability and environment context reduce risk (for example, Critical → High). Severity factors explain why the priority changed.
* **Evidence at a glance:** When available, OX displays scanner evidence, file locations, merge request information, and remediation guidance alongside OX analytics to speed triage.

### Terminology mapping

GitLab and OX use different labels for similar concepts. Use this quick map while you work.

| GitLab             | OX Security        |
| ------------------ | ------------------ |
| Projects           | Applications       |
| Merge Requests     | Pull Requests      |
| CI/CD Pipelines    | CI/CD Pipelines    |
| Container Registry | Container Registry |
| Vulnerabilities    | Issues             |
| Security Findings  | Findings           |
| Members            | Users              |

## Connection methods

For general information about connection methods, see the article Connection methods.

There are two options to connect GitLab to OX.

| Connection Method                                                                                      | Details                                                                                                         |
| ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| [Identity Provider](/get-started/onboarding-to-ox/source-control/gitlab-1/gitlab-identity-provider.md) | Use your existing identity provider connection for centralized authentication and repository access management. |
| [Personal Access Token](/get-started/onboarding-to-ox/source-control/gitlab-1/gitlab-token.md)         | Use a GitLab Personal Access Token (PAT) with the required scopes to authenticate and import repositories.      |

## Prerequisites

### Prerequisites for all connection methods

| Prerequisite   | Description                                                  |
| -------------- | ------------------------------------------------------------ |
| OX permissions | Permission to configure connectors                           |
| GitLab access  | Access to the GitLab projects and groups you want to connect |


---

# 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.ox.security/get-started/onboarding-to-ox/source-control/gitlab-1.md?ask=<question>&goal=<user_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.