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

# Certn: Remove Sprinto Access

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

Use this guide to remove the access you gave Sprinto in Certn. These steps are done in Certn, not in Sprinto. To connect Certn to Sprinto again later, see [Certn Integtation](https://docs.sprinto.com/integrations/overview/certn-integtation.md).

## Which connection method did you use?

Sprinto can be connected to Certn in 2 ways. Find the method you used, then follow the steps in that section.

| Connection method                                 | How to tell                                                                                                            |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| [Certn Legacy (API key)](#certn-legacy-api-key)   | You picked 'Certn Legacy' in Sprinto (the default) and pasted a key from Certn's Team Settings → API Keys.             |
| [Certn Centric (API key)](#certn-centric-api-key) | You picked 'Certn Centric (new platform)' in Sprinto, chose a region, and pasted a key from the Centric Client Portal. |

***

## Certn Legacy (API key) <a href="#certn-legacy-api-key" id="certn-legacy-api-key"></a>

**Who must do this:** Certn team admin

**What gets removed:** The API key you created for Sprinto is permanently deleted.

### Steps

1. Sign in to Certn at app.certn.co as a team admin.
2. Click the profile icon → **Settings**, find your team, and click **Team Settings**.
3. Click **API Keys**.
4. Find the key you created for Sprinto, click the action dropdown next to it, and click **Delete Api Key**. Any team admin can do this, even if the person who created it has left.

### Confirm it's removed

The key no longer appears under Team Settings → API Keys.

**Official guide:** [Certn docs](https://docs.certn.co/api/certn-api-v-1.0/guides/use-the-api)

***

## Certn Centric (API key) <a href="#certn-centric-api-key" id="certn-centric-api-key"></a>

**Who must do this:** Certn Centric Client Portal admin

**What gets removed:** The Centric API key you created for Sprinto is removed, so the copy Sprinto holds stops working.

### Steps

1. Sign in to the Certn Centric Client Portal (client.certn.co) for the region you picked when connecting: North America, Europe, Middle East and Africa, or Asia Pacific. Keys are separate in each region.
2. Go to **Settings** → **Integrations** → **API Keys**.
3. Find the key you created for Sprinto by its name and delete or revoke it from its row.
4. Keys belong to your Certn account, not to a person, so any admin can do this even if the person who created it has left.

### Confirm it's removed

The Sprinto key no longer appears under Settings → Integrations → API Keys in that region.

{% hint style="warning" %}
Centric keys expire 365 days after they're created, but delete the key now rather than waiting.
{% endhint %}

{% hint style="info" %}
Look for a delete or revoke option next to the key under **Settings → Integrations → API Keys**.
{% endhint %}

**Official guide:** [Certn Centric API docs](https://centric-api-docs.certn.co/reference/authentication.md)


---

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