> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finalsay-hitl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent settings

# Agent settings, assignments, and notifications

## Agent settings

Open an agent, then **Settings** (or **Configuration**) to adjust:

### Display name

Update the **name** shown for this agent in the app and in notifications.

### Default timeout

**Default timeout** is the default expiry for new approval requests, in **seconds** (minimum 30). The server applies these saved defaults whenever a create request does not override them.

* **REST** (`POST /v1/approvals`) — You may **omit** `timeout` in the JSON body; the server merges these dashboard defaults. You can also send a **partial** `timeout` object so only the fields you set override the defaults.
* **MCP** — Tools do **not** accept `timeout`. New approvals always use the dashboard defaults unless you switch to the REST Agent API for that call. The MCP adapter exposes **`request_human_approval`** and **`create_approval`** for the same `POST /v1/approvals` create (pick either name for your client); use **`get_approval_result`** to poll. See [MCP](../integrations/mcp).

### Timeout mode

* **Expire with no action** — If nobody responds before expiry, the request ends without a human choice (per product behavior).
* **Expire with predefined instruction** — If you choose this mode, you must provide **instruction text** (up to **1000** characters) that applies when the request expires that way.

Save changes when you are done.

### Delete agent

**Owners** can delete (deactivate) an agent. The app may ask you to type a confirmation phrase (such as `DELETE`) to prevent accidental removal. Deactivated agents stop accepting new approvals; historical data follows your product’s retention policy.

## Assigned members (web: Subscribers / notifications)

**Workspace owners and admins** open this screen for an agent to choose which **workspace members are assigned** to that agent. Assignment controls both **who can see the agent** in the app (and its approval queue) and **who can receive in-app and push notifications** for new requests when notifications are on.

* The list is limited to **members of the same workspace**.
* Use the checkboxes to add or remove people, then **Save assignments**. New assignees get **push and in-app notifications on** by default; a badge may show if someone has turned their own notifications off (they stay assigned and can still open the agent).
* **Members** (non-admin) only see agents they are assigned to. **Owners and admins** see every agent in the workspace.
* On **mobile and web**, each user can use a **Notify** / **Notify me** control to turn their own push and in-app notifications on or off for an agent, without being removed from the assignment.

Device-level permission (e.g. system notification settings) still applies: the app only delivers pushes when the device allows it.

**Fallback (legacy):** If an agent has **no rows** in the assignment table yet, the service may still notify **all workspace members** so someone sees new requests. If at least one assignment row exists but **everyone** has turned notifications off for that agent, the service does **not** fall back to the whole team.

## Related

* [How it works](./how-it-works)
* [Credentials](./credentials)