> 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/supabase.md).

# Supabase: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in Supabase. These steps are done in Supabase, not in Sprinto.

***

## Access review connection (sign-in window) <a href="#access-review-connection-sign-in-window" id="access-review-connection-sign-in-window"></a>

**How to tell:** Only connection method: you signed in to Supabase from Sprinto and approved access for an organization.

**Who must do this:** Supabase organization Owner or Administrator

**What gets removed:** The authorised OAuth app that gives Sprinto read access to your Supabase organization.

### Steps

1. Sign in to the Supabase dashboard and open the organization you connected.
2. Go to the organization's settings → **OAuth Apps** and scroll to Authorized apps.
3. Find the app used for Sprinto. The app may be listed as Sprinto or Truto; check the Authorized date if unsure.
4. Click the trash icon on its row, then click **Confirm** in the Revoke access for …? dialog.
5. Repeat for any other organization you connected to Sprinto.

### Confirm it's removed

The organization's Authorized apps list no longer shows the app.

{% hint style="warning" %}
Revoking removes the app for every member of the organization. Check you pick the app used for Sprinto.
{% endhint %}

**Official guide:** [Supabase docs](https://supabase.com/docs/guides/platform/sso/enterprise-mcp-authentication)


---

# 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/supabase.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.
