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

# Figma: Remove Sprinto Access

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

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

## Which connection method did you use?

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

| Connection method                                                                           | How to tell                                                                                                                         |
| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| [SCIM API token (multiple identity providers)](#scim-api-token-multiple-identity-providers) | Your Figma Enterprise organization uses Governance+ with more than one identity provider, so SCIM tokens are per identity provider. |
| [SCIM API token](#scim-api-token)                                                           | You pasted a Figma SCIM API token and tenant ID; your organization has a single identity provider set up.                           |

***

## SCIM API token (multiple identity providers) <a href="#scim-api-token-multiple-identity-providers" id="scim-api-token-multiple-identity-providers"></a>

**Who must do this:** Figma organization admin

**What gets removed:** The SCIM API token Sprinto holds for one identity provider configuration.

### Steps

1. In Figma's file browser, select **Admin** → **Settings** → **Access** → **Authentication** → **Manage identity providers** (IdP).
2. In the Identity providers table, revoke the API token for the configuration whose token you gave Sprinto.
3. If that identity provider still provisions Figma with SCIM, generate a new token for it in the same table and update your identity provider.

### Confirm it's removed

The revoked token no longer appears for that configuration in the Identity providers table.

{% hint style="warning" %}
Revoking the token stops SCIM provisioning for that identity provider until you give it a new token.
{% endhint %}

**Official guide:** [Figma help](https://help.figma.com/hc/en-us/articles/360048514653-Set-up-automatic-provisioning-via-SCIM)

***

## SCIM API token <a href="#scim-api-token" id="scim-api-token"></a>

**Who must do this:** Figma organization admin

**What gets removed:** The SCIM API token Sprinto holds (by replacing it).

### Steps

1. In Figma's file browser, select **Admin** in the sidebar, then the **Settings** tab → **Access** → **Authentication**.
2. Click **SCIM Provisioning**, then Generate API token. Figma has no delete for this token; generating a new one invalidates the token Sprinto holds.
3. If your identity provider (Okta, Entra ID, Google Workspace, OneLogin) provisions Figma with SCIM, paste the new token into its Figma provisioning settings.

### Confirm it's removed

Your identity provider's Figma provisioning test succeeds with the new token, and the old token no longer works.

{% hint style="warning" %}
Figma has one SCIM token. Generating a new one breaks your identity provider's SCIM provisioning until you update it there.
{% endhint %}

{% hint style="info" %}
After generating a new token, check that the old token no longer works.
{% endhint %}

**Official guide:** [Figma help](https://help.figma.com/hc/en-us/articles/360048514653-Set-up-automatic-provisioning-via-SCIM)


---

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