# Remove members

> **EARLY ACCESS**

> **Early access program**
>
> This is in our early access program where we closely support organizations in their usage.
>
> To have this enabled for your organization contact support@cronofy.com or your account manager.

### Description
Removes people from a Managed Organizational Unit, such as when they leave
your customer's team.

Removal takes effect immediately. The person is no longer a member, so they
aren't offered for new meetings, and your application loses access to their
calendars.

Authentication is with the access token for the Managed Organizational Unit,
returned when you
[provision](https://docs.cronofy.com/api-reference/managed-scheduling/managed-organizational-units/provision/index.md)
it. The Organizational Unit must be managed by your application.

### URL format
```
{data_center_url}/v1/organizational_unit_directory_users
```

### Example Request
```http
DELETE /v1/organizational_unit_directory_users HTTP/1.1
Host: {data_center_url}
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json; charset=utf-8

{
  "directory_users": [
    {
      "directory_user_id": "user-1002"
    }
  ]
}
```

### Example Response
```http
HTTP/1.1 202 Accepted
```

### Request Parameters
##### `data_center_url` *(required)*

The URL for the data center you want to communicate with. Possible choices are:

- `api-au.cronofy.com` - Australia
- `api-ca.cronofy.com` - Canada
- `api-de.cronofy.com` - Germany
- `api-sg.cronofy.com` - Singapore
- `api-uk.cronofy.com` - United Kingdom
- `api.cronofy.com` - United States

Find out more about [Cronofy's data centers](https://docs.cronofy.com/developers/data-centers/index.md).
##### `directory_users` *(required)*

The people to remove [`Array`](https://docs.cronofy.com/api-reference/fundamentals/data-types/index.md). Must
contain at least one person.

##### `directory_users.directory_user_id` *(required)*

Your application's identifier for the person, as given when they were
[added](https://docs.cronofy.com/api-reference/managed-scheduling/managed-organizational-units/add-member/index.md)
[`String`](https://docs.cronofy.com/api-reference/fundamentals/data-types/index.md).

### Response Parameters
This request has no response body.

### Error responses
##### 401 Unauthorized

The request was refused as the provided
[authentication credentials](https://docs.cronofy.com/api-reference/authorization/authentication/index.md)
were not recognized.

When an OAuth `refresh_token` is available then it should be used to
[request a replacement access token](https://docs.cronofy.com/api-reference/authorization/organization-connect/refresh-token/index.md)
before the request is retried.

##### 403 Forbidden

The request was refused as the access token doesn't grant the
`organizational_unit_scheduling` scope.

##### 422 Unprocessable

The request was unable to be processed due to it containing invalid
parameters, or the Organizational Unit isn't managed by your application.



---
[Read in HTML](https://docs.cronofy.com/api-reference/managed-scheduling/managed-organizational-units/remove-member/)