# Managing source control connections

Existing source-control connections live at **Settings > Integrations**. The page shows one card per integration: GitHub, GitLab, Azure DevOps, and Snyk. Clicking a card opens a drawer listing the installations the tenant has set up for that integration.

## Viewing an installation

Click the card for the integration you want to look at. A drawer opens listing each installation: the GitHub organization, GitLab instance, or Azure DevOps organization the tenant is connected to. Each row shows the owner name (which is copyable) and a delete button.

## Disconnecting

To remove an installation, click the delete icon on its row in the drawer and confirm.

What disconnecting does:

* Stops further discovery for the Seal Projects that were using this connection. They remain in source code mode (per the [one-way mode rule](/new-documentation/new-docs/creating-a-seal-project.md#mode-changes)) but stop receiving fresh signal.
* Stops the Seal GitHub App from opening new automatic PRs for the affected Seal Projects (GitHub only).

What disconnecting does not do:

* Delete the imported Seal Projects. They remain on the Projects page until you archive or delete them.
* Remove the Seal GitHub App from your GitHub organization. If you want to fully uninstall the app on the GitHub side, do that from your GitHub organization settings as well.

## Re-authenticating

Seal does not surface an in-place re-authentication control. To replace credentials (a rotated GitLab or Azure DevOps PAT, or a re-installation of the Seal GitHub App), delete the existing installation from the drawer and add it again through the **Import projects** flow on the Projects page. Existing Seal Projects re-attach to the new installation when their owner / URL match.

{% hint style="warning" %}
**VERIFY: re-attachment behavior.** Confirm with Seal that re-creating a connection automatically re-attaches existing Seal Projects to the new installation, or whether the user has to take an action. Adjust the paragraph above before publishing if the actual behavior differs.
{% endhint %}

## Related

* [Connecting GitHub](/new-documentation/new-docs/connecting-source-control/github.md), [Connecting GitLab](/new-documentation/new-docs/connecting-source-control/gitlab.md), [Connecting Azure DevOps](/new-documentation/new-docs/connecting-source-control/azure-devops.md): the original install flows.
* [Source code mode](/new-documentation/new-docs/package-discovery-mode/source-code.md): the discovery mode the connections drive, and what happens to it when the connection stops producing signal.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealsecurity.io/new-documentation/new-docs/connecting-source-control/managing-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.