--- title: "Dropbox: Configuring the Remediation Actions Integration" slug: "dropbox-configuring-the-remediation-actions-integration" updated: 2026-11-15T13:57:08Z published: 2026-11-15T13:57:08Z canonical: "knowledge.catonetworks.com/dropbox-configuring-the-remediation-actions-integration" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Dropbox: Configuring the Remediation Actions Integration ## Overview XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application. For more information, see [Mitigating Threats in XOps Stories](/v1/docs/mitigating-threats-in-xops-stories). To configure the Remediation Actions integration, you need to: 1. Configure the required settings in the SaaS application 2. Create the API connector in the CMA A XOps license is required for Remediation Actions integrations. ### Benefits of Connecting Dropbox The Dropbox Remediation Actions connector lets Cato take response actions on Dropbox team members during an investigation. It uses separate write permissions, without affecting existing Dropbox connectors, such as App Activities. - **Disable User:** Finds the team member whose email matches the requested email and suspends the account. The member loses access to the team account and is signed out of all devices. Dropbox also deletes the team's files from the member's linked computers. If the member is already suspended, the action reports that condition and succeeds. - **Revoke Sign-In Sessions:** Finds the team member in the same way and ends all web, desktop, and mobile sessions. The member must sign in again. Files on the member's computers are not deleted. The account stays active, and the action also works for suspended members. If the member has no sessions, the action reports that there was nothing to revoke and succeeds. The result shows how many sessions were found and ended. ## Configuring the Dropbox Integration To configure the integration, create the API connector in the Cato Management Application (CMA) and authorize Cato's Dropbox application as a team administrator. ### Prerequisites - A Dropbox team on a Business Plus, Advanced, or Enterprise plan - A Dropbox **team admin** who can suspend team members and manage their devices. This administrator authorizes the connector. **Disable User deletes the member's team files from their linked computers.** ### Step 1: Configure the Integration in Dropbox The connector uses Cato's pre-registered Dropbox application. You do not need to create a Dropbox app or an access token. A team administrator grants consent during Step 2. The consent page requests these permissions: - `team_info.read`: Identifies the administrator who authorized the connector so that neither action targets that administrator's account - `members.read`: Looks up the target member by email and reads their account status - `members.write`: Suspends a member for **Disable User** - `sessions.list`: Lists a member's web, desktop, and mobile sessions for **Revoke Sign-In Sessions** - `sessions.modify`: Ends a member's sessions for **Revoke Sign-In Sessions** ### Step 2: Create the API Connector in the CMA After you have set up an integration with the required application, add the details in the CMA. For Dropbox, no credentials are required. Save the connector and then complete the authorization procedure below. **To create the API connector in the CMA:** 1. From the navigation menu, click **Resources > Integrations.** 2. Click the **Configured Integrations** tab. 3. Click **New**. The **New Integration** panel opens. 4. Select the **SaaS Application** you want to add. 5. In the **Capability** drop-down, select **Remediation Actions**. 6. Add the details created during step one. - **SaaS Application:** Dropbox - **Name:** Enter a name for the integration - **Description:** Optionally, enter a description 7. Click **Save**. After saving, Cato connects to Dropbox. This can take up to 30 seconds. Complete the authorization to connect the integration. **To authorize the Dropbox connector:** 1. When prompted, click **Authorize**. A new tab opens. 2. Sign in to Dropbox as the team administrator, review the requested permissions, and click **Allow**. 3. When the success message appears, return to the CMA and refresh the page. 4. Confirm that the connector's **Connection Status** shows **Connected**. The app is visible on the **Integrated Apps** table with a **Connected** status. ## Known Limitations - **Team files are deleted from linked computers:** **Disable User** wipes the member's team files from linked computers, and the wipe cannot be undone. Unsuspending the member restores account access immediately, but the member must link the computer again to get the files back. The wipe occurs when the computer comes online with the Dropbox desktop app running. Phones and tablets are signed out because files are not synced to them. See [How to remote wipe files from a team member's device](https://help.dropbox.com/delete-restore/remote-wipe) and [How to suspend a Dropbox team member](https://help.dropbox.com/security/suspend-member). - **Authorizing administrator:** Neither action can target the administrator who authorized the connector. - **Suspension restrictions:** Dropbox cannot suspend a member who is not active, such as someone who has not accepted the invitation, or the team's last administrator. Dropbox also reports an error when the team has no available licenses. The action reports **Failed** with the Dropbox error. - **Subsequent sign-ins:** **Revoke Sign-In Sessions** leaves the account active and its password unchanged. It does not block the next sign-in. Use **Disable User** to block access. - **Partial failures:** **Revoke Sign-In Sessions** processes every session. If some sessions cannot be ended, the others are still ended. The result is **Failed**, with counts of sessions found and sessions that could not be ended. - **Connection status:** **Connected** confirms only that Cato has valid Dropbox authorization. A missing permission is reported as a **Failed** result when an action runs.