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

# Auth0: Remove Sprinto Access

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

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

***

## Access review connection (machine-to-machine app: client ID and secret) <a href="#access-review-connection-machine-to-machine-app-client-id-and-secret" id="access-review-connection-machine-to-machine-app-client-id-and-secret"></a>

**How to tell:** Only connection method: you created a Machine to Machine application in Auth0, authorised it for the Auth0 Management API, and entered your Auth0 domain, client ID and client secret when connecting Auth0 in Sprinto.

**Who must do this:** Auth0 tenant Admin

**What gets removed:** The Machine to Machine application created for Sprinto, including its access to the Auth0 Management API.

### Steps

1. Sign in to the Auth0 Dashboard and switch to the tenant you connected to Sprinto.
2. Go to **Applications** → **Applications** and open the Machine to Machine application you created for Sprinto. The app may be named Sprinto or Truto; you can match it by the Client ID you gave Sprinto.
3. Open the **Settings** tab, scroll to **Danger Zone** and click **Delete**, then confirm.
4. If you'd rather keep the application: go to **Applications** → **APIs** → **Auth0 Management API** → **Machine to Machine Applications** tab, switch off the toggle next to the Sprinto app and click **Update**. Then open the application's Settings and rotate its client secret.
5. Optional: delete any saved copies of the client secret (password manager entries, notes).

### Confirm it's removed

The application no longer appears under Applications → Applications (or its Auth0 Management API toggle shows as off). Under Monitoring → Logs, any later token requests from that Client ID show as failed (`feccft`).

{% hint style="warning" %}
Auth0 can't revoke an access token that was already issued. The last token Sprinto received keeps working until it expires (24 hours by default). Don't delete the app if other tools use the same Machine to Machine application; use step 4 instead.
{% endhint %}

**Official guide:** [Auth0 docs](https://auth0.com/docs/get-started/applications/remove-applications)


---

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