# Put one person on a role on a record

Adds ONE account to ONE role on a record, keeping everyone the role already holds, and answers the diff with the set as it now stands. Reach for it to put a colleague beside whoever is already on a deal, lead or made-board record — `put_definitions_key_rows_rowId_assignments` instead replaces the whole set with the list it is given. The record's cell keeps the primary it names; on a role nobody held, the account added becomes the primary. Naming someone already on is a no-op. Roles are agent, closer, originating_agent and processing_agent on deals, owner on leads, submissions, merchants and made boards.

Access class: `def:read`.

## Endpoint

`POST /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 |

## Request body

Content type: `application/json`.

```json
{}
```

## Responses

### 201

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"
}
```
