> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/zoho-workdrive.md).

# Zoho WorkDrive

Use Zoho WorkDrive data with Cortex Cloud

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the Zoho WorkDrive connector

Cortex Cloud supports Zoho WorkDrive teams with Super Admin or Team Admin privileges. The connection will fail for any other role.

Zoho WorkDrive uses a Self Client — a server-to-server application that you create in the Zoho API Console. No redirect URI is required and there is no browser consent screen. Cortex Cloud exchanges the Client ID and Client Secret for short-lived access tokens directly and refreshes them automatically.

> **Important:** The region cannot be changed after the instance is created. If you select the wrong region, you must delete the instance and create a new one.

To access Zoho WorkDrive, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Client ID:** The unique identifier for your Zoho Self Client application, generated in the Zoho API Console.
* **Client Secret:** The secret key used to authenticate token requests. Cortex Cloud uses the Client ID and Client Secret to obtain access tokens from the Zoho authorization server.
* **Region:** The domain suffix that corresponds to your Zoho data center. Cortex Cloud uses this value to route authentication and API calls to the correct regional endpoint.

| Region    | Domain suffix | API Console URL                   |
| --------- | ------------- | --------------------------------- |
| US        | `com`         | <https://api-console.zoho.com>    |
| Australia | `com.au`      | <https://api-console.zoho.com.au> |
| Europe    | `eu`          | <https://api-console.zoho.eu>     |
| India     | `in`          | <https://api-console.zoho.in>     |
| China     | `com.cn`      | <https://api-console.zoho.com.cn> |

Perform the following procedures in the order that they appear below.

#### Task 1: Identify Your Zoho Region

1. Sign in to your Zoho WorkDrive account and look at the URL in your browser's address bar.
2. Your region is the domain suffix that appears after `zoho.` in the URL. For example, if you sign in at `https://workdrive.zoho.eu`, your region is `eu`.
3. Identify your region and locate the corresponding API Console URL from the table above.

#### Task 2: Create a Zoho Self Client

1. Navigate to the Zoho API Console for your region and sign in with your WorkDrive Super Admin or Team Admin account.
2. Click **GET STARTED** (or **ADD CLIENT** if you already have existing applications).
3. Select **Self Client** as the application type.
4. Enter a **Client Name** (for example, `Cortex_WorkDrive_Integration`).
5. Click **CREATE**, then confirm with **OK**.

#### Task 3: Retrieve Your Client ID and Client Secret

1. Open the **Client Secret** tab of your newly created Self Client.
2. Copy the **Client ID** and **Client Secret** and store them securely.

   > Do not continue to the next step unless you have copied both values. You must provide them to Cortex Cloud during the onboarding process.

#### Task 4: Connect Zoho WorkDrive to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Zoho WorkDrive.
4. Under **Recommended**, hover over the new Zoho WorkDrive integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Client ID**, **Client Secret**, and **Region** details.

   Cortex Cloud requests the following read-only scopes when it exchanges your credentials for a token:

   * `WorkDrive.users.READ`

   * `WorkDrive.team.admin.READ`

   * `WorkDrive.team.READ`

   > **Note:** If your tenant does not expose the fine-grained `WorkDrive.team.READ` scope, Zoho may require the broader `team` scope instead. Contact Zoho support if the token request is rejected for a missing scope.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that Zoho WorkDrive is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/zoho-workdrive.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.
