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

# Aikido Security: Remove Sprinto Access

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

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

***

## Aikido sends findings to Sprinto <a href="#aikido-sends-findings-to-sprinto" id="aikido-sends-findings-to-sprinto"></a>

**How to tell:** Only one way to connect: set up from Aikido (Settings → Integrations → Sprinto) with a Sprinto API key.

**Who must do this:** Aikido workspace admin

**What gets removed:** The Sprinto integration in Aikido, which stores the Sprinto API key and pushes findings every 24 hours.

### Steps

1. Sign in to Aikido as a workspace admin and go to **Settings** → **Integrations** → **Sprinto**.
2. Open the integration's management options and remove it (on Aikido's other integration pages this option is called Remove Integration), then confirm.
3. Check that Sprinto no longer shows as connected under **Settings** → **Integrations**.

### Confirm it's removed

Sprinto shows as not connected in Aikido (the Add Sprinto integration option is available again).

{% hint style="info" %}
If you don't see **Remove Integration**, open **Settings → Integrations → Sprinto** in Aikido and look for the option to remove or disconnect the integration.
{% endhint %}

**Official guide:** [Aikido docs](https://help.aikido.dev/compliance-and-reporting/iso-27001-and-soc-2-compliance-overview/sprinto-compliance-integration)


---

# 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/aikido-security.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.
