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

# Zoho People: Remove Sprinto Access

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

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

***

## Sprinto Zoho app (sign-in with Zoho) <a href="#sprinto-zoho-app-sign-in-with-zoho" id="sprinto-zoho-app-sign-in-with-zoho"></a>

**How to tell:** Only method: you clicked Connect for Zoho People in Sprinto and approved Zoho's consent screen.

**Who must do this:** The Zoho user who connected (a Zoho People admin); if they've left, a Zoho Directory or Zoho One admin who can reset passwords

**What gets removed:** Sprinto's OAuth grant to Zoho People is deleted from the connecting user's Zoho account.

### Steps

1. As the person who connected Sprinto, sign in to Zoho Accounts for your data centre: accounts.zoho.com (US), accounts.zoho.eu (EU), accounts.zoho.in (India), accounts.zoho.com.au (Australia), accounts.zoho.jp (Japan), accounts.zoho.uk (UK), accounts.zoho.sa (Saudi Arabia), accounts.zoho.ae (UAE), accounts.zoho.sg (Singapore) or accounts.zohocloud.ca (Canada).
2. Click **Sessions** in the left menu, then click **Connected Apps**.
3. Find the app Sprinto used. The app may be listed as Sprinto.
4. Hover over the app, click **Revoke Access**, then click **Yes, Proceed**. If you don't see Revoke Access, click the entry, then click **Delete**.
5. If that person has left and can't sign in, an admin clears their app access instead. In Zoho Directory: **Admin Panel** → **User Management** → click the user → **Reset Password**, enter or generate a new password, select **Clear mobile sessions** and API tokens, enter your own password, then click **Reset**. In Zoho One: **Admin Panel** → **User Management** → click the user → **Reset Password**, select **Clear mobile sessions** and API tokens, enter your own password, then click **Yes, Confirm**.

### Confirm it's removed

Sprinto no longer appears under Sessions → Connected Apps for the user who connected. If you used the admin reset, Sprinto's connection stops working.

{% hint style="warning" %}
If you also connected Sprinto's Zoho Mail, Endpoint Central or ServiceDesk Plus integrations, you may see more than one Sprinto entry. Remove only the one for Zoho People; if you can't tell them apart, reconnect the others afterwards. The admin reset in step 5 ends every app connection that person made, not just Sprinto's.
{% endhint %}

{% hint style="info" %}
In step 4, the button may be labelled **Revoke Access** or **Delete**. If you use the admin reset in step 5, check afterwards that Sprinto's Zoho connection has stopped working.
{% endhint %}

**Official guide:** [Zoho Accounts help](https://help.zoho.com/portal/en/kb/accounts/manage-your-zoho-account/articles/sessions-zohoaccounts)


---

# 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/zoho-people.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.
