> 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/google-cloud-gcp.md).

# Google Cloud (GCP): Remove Sprinto Access

Remove the access Sprinto was given in Google Cloud (GCP). Covers every way Sprinto can be connected to Google Cloud (GCP) and the steps to take in Google Cloud (GCP) for each.

Use this guide to remove the access you gave Sprinto in Google Cloud (GCP). These steps are done in Google Cloud (GCP), not in Sprinto. To connect Google Cloud (GCP) to Sprinto again later, see [GCP Integration](https://docs.sprinto.com/integrations/overview/gcp-integration.md), [GCP Integration (via Cloud Shell)](https://docs.sprinto.com/integrations/overview/gcp-integration-via-cloud-shell.md) or [GCP Integration (via Access Management)](https://docs.sprinto.com/integrations/overview/gcp-integration-via-access-management.md).

## Which connection method did you use?

Sprinto can be connected to Google Cloud (GCP) in 2 ways. Find the method you used, then follow the steps in that section.

| Connection method                                                                           | How to tell                                                                                                                                                    |
| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Keyless setup (workload identity federation)](#keyless-setup-workload-identity-federation) | The project where you ran the script has service account `sprinto-serviceaccount` and a workload identity pool `sprinto-wif-pool`; no JSON key was downloaded. |
| [Service account key (JSON key file)](#service-account-key-json-key-file)                   | The project has service account `sprinto-service-account` and you uploaded a JSON key file (`sa-private-key.json`) to Sprinto.                                 |

***

## Keyless setup (workload identity federation) <a href="#keyless-setup-workload-identity-federation" id="keyless-setup-workload-identity-federation"></a>

**Who must do this:** Project IAM Admin and Service Account Admin on the connected projects, Organization Admin for the org-level role, and IAM Workload Identity Pool Admin

**What gets removed:** Sprinto's role bindings, its service account and its workload identity pool.

### Steps

1. In the Google Cloud console go to **IAM & Admin** → **IAM**, select each project you connected, find `sprinto-serviceaccount@…iam.gserviceaccount.com`, click **Edit principal**, click **Delete** next to each role (Compute Viewer, Security Reviewer, Monitoring Editor) and click **Save**.
2. On the same IAM page, select your organization. If the principal has Cloud Asset Viewer, click **Edit principal**, delete that role and click **Save**.
3. In the project where you ran the script, go to **IAM & Admin** → **Service accounts**, select `sprinto-serviceaccount` and click **Delete**, then confirm.
4. Go to **IAM & Admin** → **Workload Identity Pools**, open Sprinto GCP Identity Pool (`sprinto-wif-pool`), click **Delete pool**, then **Delete**. Delete the whole pool, not just its provider.

### Confirm it's removed

`sprinto-serviceaccount` no longer appears on the IAM or Service accounts pages, and `sprinto-wif-pool` is not listed on Workload Identity Pools (it only shows under Show deleted pools and providers).

{% hint style="warning" %}
A deleted pool stays reserved for 30 days; Sprinto's setup script restores it automatically if you reconnect within that time.
{% endhint %}

**Official guide:** [Google Cloud docs](https://docs.cloud.google.com/iam/docs/manage-workload-identity-pools-providers)

***

## Service account key (JSON key file) <a href="#service-account-key-json-key-file" id="service-account-key-json-key-file"></a>

**Who must do this:** Project IAM Admin and Service Account Admin (or Service Account Key Admin) on the connected projects; Organization Admin for the org-level role

**What gets removed:** The JSON key, Sprinto's role bindings and the `sprinto-service-account` service account.

### Steps

1. In the Google Cloud console go to **IAM & Admin** → **Service accounts** in the project where you ran the script, click `sprinto-service-account@…`, open the **Keys** tab and click **Delete** for each key.
2. Go to **IAM & Admin** → **IAM**, select each project you connected, find `sprinto-service-account@…`, click **Edit principal**, click **Delete** next to each role (Security Reviewer, Compute Viewer, Monitoring Editor) and click **Save**.
3. On the **IAM** page, select your organization. If the principal has Cloud Asset Viewer, click **Edit principal**, delete that role and click **Save**.
4. Back on Service accounts, select `sprinto-service-account`, click **Delete** and confirm.
5. Optional: delete stored copies of the key — the downloaded `sa-private-key.json` and the copy in your Cloud Shell home folder (`rm ~/sa-private-key.json`). This doesn't affect reconnecting.

### Confirm it's removed

`sprinto-service-account` no longer appears on the Service accounts or IAM pages of any connected project or the organization.

**Official guide:** [Google Cloud docs](https://docs.cloud.google.com/iam/docs/keys-create-delete)


---

# 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/google-cloud-gcp.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.
