> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.34.0/set-up/vcs-providers/gitlab.com.md).
# GitLab
For using repositories from Gitlab.com with Terrakube workspaces and modules you will need to follow these steps:
{% hint style="info" %}
**Manage VCS Providers** permission is required to perform this action, please check [Team Management](/2.34.0/set-up/organizations/team-management.md) for more info.
{% endhint %}
Navigate to the desired organization and click the **Settings** button, then on the left menu select **VCS Providers**
{% hint style="info" %}
If you prefer, you can add a new VCS Provider directly from the [Create workspace](/2.34.0/run-terraform/workspaces/creating-workspaces.md) or Create Module screen.
{% endhint %}
Click the **Gitlab** button
In the next screen click the link to [register a new OAuth Application](https://gitlab.com/-/profile/applications) in Gitlab
On Gitlab, complete the required fields and click **Save application** button
Field
Description
Name
Your application name, for example you can use your organization name.
Redirect URI
Copy the Redirect URI from the UI
Scopes
Only api should be checked
{% hint style="info" %}
You can complete the fields using the information suggested by terrakube in the VCS provider screen
{% endhint %}
In the next screen, copy the **Application ID** and **Secret**
Go back to Terrakube to enter the information you copied from the previous step. Then, click the **Connect and Continue** button.
You will see a Gitlab window, click the **Authorize** button to complete the connection
Finally, if the connection was established successfully, you will be redirected to the VCS provider’s page in your organization. You should see the connection status with the date and the user that created the connection.
And now, you will be able to use the connection in your workspaces and modules:
---
# 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.terrakube.io/2.34.0/set-up/vcs-providers/gitlab.com.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)