---
title: Disable a single security identity
slug: '84'
canonical_url: https://docs.coveo.com/en/84/
collection: index-content
source_format: adoc
---
# Disable a single security identity
:figure-caption!:

Disabling a single [security identity](https://docs.coveo.com/en/240/) in the [security identity provider](https://docs.coveo.com/en/242/) of a secured Push [source](https://docs.coveo.com/en/246/) is especially useful during service testing or when you need to perform a small [security identity update](https://docs.coveo.com/en/244/).

Use the `Delete a security identity` request only to disable a specific security identity in a certain security identity provider.
To maximize efficiency and comply with [API consumption limits](https://docs.coveo.com/en/63/), don't use this request repeatedly to disable many security identities in a security identity provider.
If this is what you need to do, depending on what you want to achieve, you should either use:

* [Batch update requests](https://docs.coveo.com/en/55/).

* The [`Delete old security identities`](https://docs.coveo.com/en/33/) request.

> **Note**
>
> For legacy reasons, the path of this request uses the word _permissions_ instead of _identities_.
> While those two concepts are related, they have entirely different meanings.
> Remember that this request actually allows you to interact with [security identities](https://docs.coveo.com/en/240/), not item [permissions](https://docs.coveo.com/en/223/).

## Request template

**US East region**
[%collapsible%open]
#### [source,http,subs=attributes]
```
DELETE https://api.cloud.coveo.com/push/v1/organizations/<MyOrganizationId>/providers/<MySecurityIdentityProviderId>/permissions HTTP/1.1
​
Content-Type: application/json
Accept: application/json
Authorization: Bearer <MyAccessToken>
```
#### .Canada region
<details><summary>Details</summary>

[source,http,subs=attributes]
```
DELETE https://api-ca.cloud.coveo.com/push/v1/organizations/<MyOrganizationId>/providers/<MySecurityIdentityProviderId>/permissions HTTP/1.1
​
Content-Type: application/json
Accept: application/json
Authorization: Bearer <MyAccessToken>
```

</details>

**Ireland region**
<details><summary>Details</summary>

[source,http,subs=attributes]
```
DELETE https://api-eu.cloud.coveo.com/push/v1/organizations/<MyOrganizationId>/providers/<MySecurityIdentityProviderId>/permissions HTTP/1.1
​
Content-Type: application/json
Accept: application/json
Authorization: Bearer <MyAccessToken>
```

</details>

**Australia region**
<details><summary>Details</summary>

[source,http,subs=attributes]
```
DELETE https://api-au.cloud.coveo.com/push/v1/organizations/<MyOrganizationId>/providers/<MySecurityIdentityProviderId>/permissions HTTP/1.1
​
Content-Type: application/json
Accept: application/json
Authorization: Bearer <MyAccessToken>
```

</details>

Request parameters:

**Parameters**
<details><summary>Details</summary>

In the request path:

* Replace `<MyOrganizationId>` with your [organization ID](https://docs.coveo.com/en/148/).

* Replace `<MySecurityIdentityProviderId>` with the actual ID of the target security identity provider.
See [Create a security identity provider for a secured Push source](https://docs.coveo.com/en/85/) for details.

In the `Authorization` HTTP header:

* Replace `<MyAccessToken>` with a Push source API key that grants the [set of privileges required to push security identities](https://docs.coveo.com/en/1546#api-key) to the security identity provider.

</details>

Request body:

```json
{
  "identity": {
    "name": <MySecurityIdentityName>,
    "type": <"GROUP"|"UNKNOWN"|"USER"|"VIRTUAL_GROUP">
  }
}
```

**Parameters**
<details><summary>Details</summary>

* Replace `<MySecurityIdentityName>` with the [name](https://docs.coveo.com/en/78#name-string-required) of the security identity to disable.

* Replace `<"GROUP"|"UNKNOWN"|"USER"|"VIRTUAL_GROUP">` with the entity type of the security identity to delete.

</details>

Successful response: `202 Accepted`

## Sample request

The following example shows how to disable a single-user security identity in a security identity provider.

```http
DELETE https://api.cloud.coveo.com/push/v1/organizations/mycoveocloudv2organizationg8tp8wu3/providers/My%20Secured%20Push%20Source%20Security%20Identity%20Provider/permissions HTTP/1.1
​
Content-Type: application/json
Accept: application/json
Authorization: Bearer **********-****-****-****-************
```

Request body:

```json
{
  "identity": {
    "name": "asmith@example.com",
    "type": "USER"
  }
}
```