> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/agent-permission-settings/openapi.json](/docs/api/agent-permission-settings/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Agent permissions: Get Ken's agent permissions

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Agent permissions](/docs/api/agent-permission-settings.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Get Ken's agent permissions

`GET /v1/agent-permission-settings` - operationId `agent-permission-settings.get`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 12,000 requests a minute per API key |

Returns every action with its mode, always all seven in page order (and `engage_linkedin` as the eighth
where Kenso has switched it on). An action the workspace never set has its
default and `updatedAt` null. The defaults: `send_email`, `send_linkedin` and `build_assets`
ask first and the others run on their own; where Kenso has switched the new defaults on, `send_email` and
`send_linkedin` read `runs_everything` and `engage_linkedin` `runs_on_its_own`, and on a client
workspace those three read `asks_first` until the client's yes is stored. Where Kenso has not switched them on, a
`runs_everything` saved earlier reads `runs_on_its_own`, which is how Ken follows it then. `available` is false for an action Kenso does not follow yet: its mode cannot
change. `book_meetings` reads `asks_first` with `lockedReason` `reply_agent_not_autonomous`
while the reply agent is off or not autonomous. That `asks_first` is not the stored mode: send the row back in
a PATCH only to store `asks_first`. `clientWorkspace` is true for a workspace run for a client.

Errors:

- `404 not_found`: the workspace does not have the `agent_permissions` feature.

Open to any workspace member except a Client seat.

Needs the `agent_permissions` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/agent-permission-settings/GET/v1/agent-permission-settings)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `AgentPermissionSettings`.

| Field | Type | Description |
| --- | --- | --- |
| `permissions` | array of AgentPermission | Every action, always, in page order: seven, and `engage_linkedin` as the eighth where Kenso has switched it on. |
| `clientWorkspace` | boolean | The workspace is run for a client (a white-label child, or marked so by its team). Then switching `send_email`, `send_linkedin` or `engage_linkedin` to `runs_on_its_own` needs `clientYes`. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/agent-permission-settings" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "permissions": [
      {
        "action": "send_email",
        "mode": "string",
        "available": true,
        "lockedReason": "string",
        "updatedAt": "2026-09-23T15:02:11Z"
      }
    ],
    "clientWorkspace": true
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### AgentPermission

One action and its mode.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | no | `send_email`, `send_linkedin`, `research_accounts`, `scan_signals`, `build_assets`, `run_crm_workflows` or `book_meetings`; and `engage_linkedin` (follows and likes on LinkedIn) where Kenso has switched it on. |
| `mode` | string | no | `asks_first` (Ken asks a person before it acts) or `runs_on_its_own` (Ken acts without a per-item approval; every other guard still applies). The stored mode, else the action's default. Where Kenso has switched it on, `send_email` and `send_linkedin` can also read `runs_everything` (their default there): Ken then also sends, without approval, emails and LinkedIn messages nobody in the workspace asked for or is working on, such as a draft its quality check flagged, a draft Ken wrote again, or a message an API key or an agent wrote. A message a member asked Ken to draft, edited or acted on still waits for approval. |
| `available` | boolean | no | Whether the mode can be changed now. False: Kenso does not follow this setting yet, so a PATCH of it answers `action_not_available`. |
| `lockedReason` | string | no | Why the mode is held where it is, or null. `reply_agent_not_autonomous` (book_meetings only): Ken books only while the reply agent is on and autonomous, so the mode reads `asks_first` until then. |
| `updatedAt` | string (date-time) | no | When the mode was last set, in UTC; null for an action the workspace never set. |
