---
title: "Who a user field may be set to"
description: "List the users this user field accepts: app users who are not suspended, limited to the field's roles when it has any."
canonical: "https://grid82.com/docs/app-api/fields/people"
updated: "2026-11-20"
---

# Who a user field may be set to

`GET https://your-suite.grid82.app/your-app/v1/tables/{tableId}/fields/{fieldId}/people`

List the users this user field accepts: app users who are not suspended, limited to the field's roles when it has any.

> **Note: Generic contract**
>
> Your own version of this operation, with your tables and the fields you can read, is in
> your app's document: `https://{suite}.grid82.app/{app}/v1/openapi.json`, behind your credential.
> [Why each person gets their own](/docs/start/key-concepts#why-an-app-has-an-api-of-its-own).

Answered only to someone who may edit the field. A write accepts any of them by user ID, email, or exact name, and keeps people the record already holds.

Requires the `records:read` scope. Operation `fields.people`. MCP tool `fields_people`. CLI: `grid82 fields people` (`npx @grid82/cli`).

## Path parameters

| Name      | Type   | Required | Description |
| --------- | ------ | -------- | ----------- |
| `tableId` | string | yes      |             |
| `fieldId` | string | yes      |             |

**Authorizations**

- `Authorization` (bearer, in header, required)

## Response

**200**: Success

- `data` (`object[]`, required)
- `data.userId` (`string`, required)
- `data.name` (`string,null`, required)
- `data.email` (`string,null`, required)

```json
{
  "data": [
    {
      "userId": "<string>",
      "name": null,
      "email": null
    }
  ]
}
```

**4XX**: Refused

- `error` (`object`, required)
- `error.code` (`enum<string>`, required, one of: `not_found, forbidden, unauthenticated, validation_failed, conflict, rate_limited, payment_required, not_implemented, internal`)
- `error.message` (`string`, required)
- `error.details` (`Record<string, unknown>`)

```json
{
  "error": {
    "code": "not_found",
    "message": "<string>",
    "details": {}
  }
}
```

**Example request**

```bash
curl --request GET \
  --url 'https://your-suite.grid82.app/your-app/v1/tables/<tableId>/fields/<fieldId>/people' \
  --header 'Authorization: Bearer <token>'
```
