> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-setup/auto-remediations/disable-accounts/google-workspace-disable-accounts.md).

# Google Workspace: Disable Accounts

*This guide is the first step of a larger process to enable auto remediations. After completing the steps on this page, you will be instructed to return to the* [*Enable an Auto Remediation in Workbench*](/workbench-setup/auto-remediations/enable-an-auto-remediation-in-workbench.md) *guide to finish your setup.*

## How It Works <a href="#h_01jh8ncdq41ghs4zvz4pj1n7wp" id="h_01jh8ncdq41ghs4zvz4pj1n7wp"></a>

If our SOC identifies an account (username or email address) that is compromised and must be disabled, Workbench completes the action automatically and logs the user out of their session. You have the option to restrict these actions to specific accounts by configuring an allow or deny list (the accounts must first be added as context, and then the list can be configured in Workbench; see [Step 3](#h_01jh5zhtqthkyym38xnhr25vgj)).

{% hint style="info" %}
Some vendors refer to disabling a user account as blocking a user, suspending a user, changing user status, removing a user from the org, or locking a user account.
{% endhint %}

## Step 1: Add OAuth Scopes to Google <a href="#h_01fs7gwjh91x8crymftnked1kr" id="h_01fs7gwjh91x8crymftnked1kr"></a>

1. Open the Google Workspace admin console:  <https://admin.google.com/ac/owl/domainwidedelegation>.
2. Navigate to **Security > API Controls > Manage Domain Wide Delegation**.
3. Select **Edit** next to the Expel API client.
4. Scroll to the bottom and add the following OAuth scopes:
   * <https://www.googleapis.com/auth/admin.directory.user&#x20>;
   * <https://www.googleapis.com/auth/admin.directory.user.security>

     <div align="left"><figure><img src="/files/EAWzo3QUK9D3vmThwbgY" alt="The two OAuth scopes are added on the Edit scopes screen." width="295"><figcaption></figcaption></figure></div>
5. Select **Authorize**.

## Step 2: Add OAuth Scopes to Workbench <a href="#id-01fyq4stnpj06pw23g3q66eqxx" id="id-01fyq4stnpj06pw23g3q66eqxx"></a>

1. In a new browser tab, [log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. Navigate to **Organization Settings > Security Devices**.
3. Find **Google Workspace** in the list.
4. Select the **down arrow** in the Google Workspace row, and select **View & Edit**.
5. Scroll to the end of API scopes field and add the OAuth scopes:
   * <https://www.googleapis.com/auth/admin.directory.user&#x20>;
   * <https://www.googleapis.com/auth/admin.directory.user.security>

     <div align="left"><figure><img src="/files/FkQRfcbQ5YqVvZ5xP9hp" alt="The two OAuth scopes are added to the API scopes field, separated by a comma." width="445"><figcaption></figcaption></figure></div>
6. Select **Save**.

## Step 3: Update Your Context <a href="#h_01jh5zhtqthkyym38xnhr25vgj" id="h_01jh5zhtqthkyym38xnhr25vgj"></a>

**If you do not want to specify any accounts for a "do not disable" or "always disable" list, and instead wish for Expel to automatically disable&#x20;*****all*****&#x20;identified accounts, skip to** [**Step 4**](#h_01jgycgywj4m9tc7j443dvsmf1)**.**

Working with your Customer Success Manager, prepare to create an allow or deny list by adding accounts as [org context](/workbench-reference/expel-terminology.md#org-context) for your environment. You will then be able to select those accounts as "Never disable" or "Always disable" assets when you enable the auto remediation in Workbench.

{% hint style="info" %}
If our SOC identifies an account that must be disabled and you have created either an allow ("Always disable") or deny ("Never disable") list in Workbench, any accounts falling outside of those parameters are assigned to you as actions rather than being disabled automatically.
{% endhint %}

## Step 4: Return to the Main Setup Guide <a href="#h_01jgycgywj4m9tc7j443dvsmf1" id="h_01jgycgywj4m9tc7j443dvsmf1"></a>

Your Google Workspace device is now ready for the Disable Accounts auto remediation. You should now do one of the following:

* **If you do not need to set up any other devices for this auto remediation**, you can return to the [Enable an Auto Remediation in Workbench](/workbench-setup/auto-remediations/enable-an-auto-remediation-in-workbench.md) guide to finish Step 2 of the process.
* **If you need to set up additional devices for this auto remediation, or wish to use this device with multiple auto remediations**, be sure to [complete those setup guides as well](/workbench-setup/auto-remediations.md) before returning to the [Enable an Auto Remediation in Workbench](/workbench-setup/auto-remediations/enable-an-auto-remediation-in-workbench.md) guide to finish Step 2 of the process. *Make sure to follow the setup guide that is specific to your auto remediation, as device setup instructions are unique to each auto remediation and device.*


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.expel.io/workbench-setup/auto-remediations/disable-accounts/google-workspace-disable-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.