# Put one person in a role on a record

Puts one member in one role on one DEAL by writing that role's person cell — `opener` or `closer` — and answers the row; an empty `assignee` clears the role. This is the single-cell route. `put_definitions_key_rows_rowId_assignments` is the one that replaces a role's whole SET, works on every pack page, and spells the deal's opener `agent`; both write the same column, so they cannot disagree. Deals only.

Access class: `def:read`.

## Endpoint

`PUT /v1/definitions/{key}/rows/{rowId}/assignee/{role}`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| role | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "assignee": "string"
  },
  "params": {
    ":key": "string",
    ":role": "string",
    ":rowId": ""
  },
  "query": {}
}
```

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "archived_at": "string",
    "assignees": {},
    "cells": {},
    "createdBy": "string",
    "display": {},
    "externalId": "",
    "groupId": "",
    "id": "",
    "position": 1,
    "source": "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"
}
```