> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/remove-integration-access/gitlab.md).

# GitLab: Remove Sprinto Access

Remove the access Sprinto was given in GitLab. Covers every way Sprinto can be connected to GitLab and the steps to take in GitLab for each.

Use this guide to remove the access you gave Sprinto in GitLab. These steps are done in GitLab, not in Sprinto. To connect GitLab to Sprinto again later, see [GitLab Integration](https://docs.sprinto.com/integrations/overview/gitlab-integration.md) or [GitLab Integration - Bring your own app](https://docs.sprinto.com/integrations/overview/self-hosted-gitlab-integration.md).

## Which connection method did you use?

Sprinto can be connected to GitLab in 3 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                           | How to tell                                                                                                                |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| [GitLab.com (Sprinto app)](#gitlab-com-sprinto-app)                                         | You clicked Connect without ticking 'Are you using self-hosted GitLab Service?' and approved access on gitlab.com.         |
| [Self-managed GitLab (your OAuth application)](#self-managed-gitlab-your-oauth-application) | You ticked 'Are you using self-hosted GitLab Service?' and entered a Hosted service URL, Application ID and Client Secret. |
| [Vulnerability scanner (access token)](#vulnerability-scanner-access-token)                 | GitLab was connected under Vulnerability scanners using a project, group or personal access token.                         |

***

## GitLab.com (Sprinto app) <a href="#gitlab-com-sprinto-app" id="gitlab-com-sprinto-app"></a>

**Who must do this:** The GitLab user who authorized the connection; group Owner for the admin path

**What gets removed:** Sprinto's OAuth authorization on the GitLab.com account that connected.

### Steps

1. The person who connected: on GitLab.com, select your avatar (upper-right) → **Edit profile**.
2. In the left sidebar, select **Access** → **Applications**.
3. In the **Authorized applications** section, find Sprinto's app and select **Revoke**. The app may be listed as Sprinto.
4. If that person has left, a group Owner removes them from the group: group → **Manage** → **Members** → vertical ellipsis next to them → **Remove member** → **Remove member**.

### Confirm it's removed

Sprinto no longer appears under Authorized applications for the user who connected.

**Official guide:** [GitLab docs](https://docs.gitlab.com/integration/oauth_provider/)

***

## Self-managed GitLab (your OAuth application) <a href="#self-managed-gitlab-your-oauth-application" id="self-managed-gitlab-your-oauth-application"></a>

**Who must do this:** Owner of the OAuth application: the user who created it, a group Owner (group application) or a GitLab administrator (instance-wide application)

**What gets removed:** The OAuth application you created on your GitLab instance for Sprinto, with all its grants and tokens.

### Steps

1. Find the OAuth application you created for Sprinto (its Application ID matches the one you entered in Sprinto). User-owned: avatar → **Edit profile** → **Access** → **Applications**.
2. Group-owned: open the group → **Settings** → **Applications**. Instance-wide: **Admin** → **Applications** (administrator only).
3. On the application's row, click the trash icon (Destroy) and confirm. In the Admin area, click **Destroy** in the **Confirm destroy application** box. Deleting it also deletes all grants and tokens issued through it.
4. If you can't find or delete it, the person who connected can revoke access: avatar → **Edit profile** → **Access** → **Applications** → **Authorized applications** → **Revoke** on its row, then confirm.
5. Optional: delete saved copies of the application's Client Secret.

### Confirm it's removed

The application is gone from the Applications list, and nothing for it remains under the connecting user's Authorized applications.

**Official guide:** [GitLab docs](https://docs.gitlab.com/integration/oauth_provider/)

***

## Vulnerability scanner (access token) <a href="#vulnerability-scanner-access-token" id="vulnerability-scanner-access-token"></a>

**Who must do this:** Project Maintainer/Owner or group Owner (project/group tokens); the token's user (personal token); group Owner (Ultimate) or administrator for the admin path

**What gets removed:** The GitLab access token created for Sprinto's vulnerability scanning.

### Steps

1. Project token: open the project → **Settings** → **Access tokens**, select **Revoke** next to the token, then **Revoke**.
2. Group token: open the group → **Settings** → **Access tokens**, select **Revoke** next to the token, then **Revoke**.
3. Personal token: avatar → **Edit profile** → **Access** → **Personal access tokens** → vertical ellipsis next to the token → **Revoke** → **Revoke**.
4. If the token's owner has left (Ultimate): group → **Secure** → **Credentials**, or on self-managed Admin → **Access** → **Credentials**, then Revoke next to the token.
5. If you created a dedicated GitLab user only for this connection, delete that user too.
6. Optional: delete saved copies of the token.

### Confirm it's removed

The token shows as revoked/inactive (it no longer appears in the active tokens list).

{% hint style="warning" %}
GitLab doesn't let you permanently delete tokens: a revoked token stays listed as inactive (group and project tokens are cleared after 30 days). This doesn't block reconnecting.
{% endhint %}

**Official guide:** [GitLab docs](https://docs.gitlab.com/user/project/settings/project_access_tokens/)


---

# 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.sprinto.com/integrations/remove-integration-access/gitlab.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.
