# Take one person off a role on a record

Takes ONE person out of ONE role on a record, leaving the rest of that role's set standing, and answers the diff. Its own door rather than a PUT of the remaining list, because two people each removing a different colleague would otherwise overwrite each other. If the person removed was the one the record's cell named, the cell moves to whoever remains rather than being cleared. A person who does not hold the role is a 404.

Access class: `def:read`.

## Endpoint

`DELETE /v1/definitions/{key}/rows/{rowId}/assignments/{role}/{accountId}`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| role | path | string | Yes |
| accountId | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "added": [
      "string"
    ],
    "assignees": [
      {
        "accountId": "",
        "assignedAt": "string",
        "assignedBy": "string",
        "displayName": "string",
        "email": "string",
        "primary": "string"
      }
    ],
    "removed": [
      "string"
    ],
    "role": "string"
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```