> 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/okta-disable-accounts.md).

# Okta: 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 2](#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 %}

## Prerequisites <a href="#h_01jh8yk2yky81h67dwkq0zm0a3" id="h_01jh8yk2yky81h67dwkq0zm0a3"></a>

1. You must have admin privileges in Okta (either Super Administrator privileges *or* Report Administrator + Group Administrator permissions).
2. You must have admin access in Workbench, as auto remediations are enabled at the organization level.

## Step 1: Grant Necessary Permissions <a href="#h_01jh8xj51d1dhrdzeb4v1kj509" id="h_01jh8xj51d1dhrdzeb4v1kj509"></a>

The Okta API token uses the Read-Only Admin permission in Workbench and the Auto Disable Accounts feature requires the Group Admin permission. In Okta, API tokens have the same permissions as the user who creates them and, if the user permissions change, the API token permissions also change.

As a result, you have the following options:

* If you want to edit the existing user permissions, choose [Option 1](#id-01fqhx9dx1wdr1pygen54vcyy4) (you must have Super Administrator privileges to choose this option).
* If you want to generate a new API token with the required permissions and then update your security device in Workbench, choose [Option 2](#id-01frndpr50ynfykpsywztadmvx) (you must have Report Administrator + Group Administrator permissions to choose this option).

### Option 1: Edit Existing User Permissions <a href="#id-01fqhx9dx1wdr1pygen54vcyy4" id="id-01fqhx9dx1wdr1pygen54vcyy4"></a>

The user you edit should be the one that created the API token, which is the same user you configured in [Okta Workforce Identity Setup for Workbench](/connect-your-technology/l-p-integrations/okta-workforce-identity-setup-for-workbench.md).

1. Log in to your Okta organization as a user with Super Administrator permissions.
2. Add the Report Administrator + Group Administrator permissions to the existing user for Expel.

### Option 2: Generate a New API Token <a href="#id-01frndpr50ynfykpsywztadmvx" id="id-01frndpr50ynfykpsywztadmvx"></a>

1. Log in to your Okta organization as a user with Report Administrator + Group Administrator permissions.
2. Follow Step 2 of the [Okta Workforce Identity Setup for Workbench](/connect-your-technology/l-p-integrations/okta-workforce-identity-setup-for-workbench.md) to generate a new API token.
3. In a new browser tab, [log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
4. Navigate to **Settings > Security Devices**.
5. Find **Okta** in the security device list.
6. On the right side of the Okta row, select the **down arrow**, and select **View & Edit**.
7. Replace the **API Token** with the newly generated token.
8. Select **Save**.

## Step 2: 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 3**](#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 3: Return to the Main Setup Guide <a href="#h_01jgycgywj4m9tc7j443dvsmf1" id="h_01jgycgywj4m9tc7j443dvsmf1"></a>

Your Okta 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/okta-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.