# Approvers without Slack

> Who can approve a held action on a workspace that has no Slack workspace connected, how the list is set, and what the API refuses.

Source: https://docs.atensecurity.com/docs/operations/approvers

A held action (`STEP_UP`) waits for a person to approve or deny it. Where a workspace has a Slack
workspace connected, [Slack approvals](https://docs.atensecurity.com/docs/operations/slack-approvals) names the reviewers. This page
covers the other case: a workspace with no Slack, such as a dedicated deployment, where approvals are
made through the dashboard, `thothctl approvals resolve` or an MCP client.

**Warning:**
  The approver list is set in the dashboard (Settings → Approvers), through the workspace API,
  `thothctl approvals approvers`, the `thoth_tenant_approvers` Terraform resource (also available in the
  Pulumi provider), the MCP server's `preview_approvers` or Ask Thoth. All need a signed-in organization
  administrator; an API key is refused. Until a list is set, nobody can approve on such a workspace and a
  hold ends in `BLOCK` when it times out.

## The rules

- **An explicit list.** The workspace keeps a list of up to 50 WorkOS users. Only people on the list can
  approve or deny a held action. There is no "all admins" mode, and an **empty list means nobody can
  approve**.
- **Active members only.** Every person on the list must be a verified, active member of your
  organization when the list is saved, and must still be an active member when they resolve a hold. A
  member removed from the organization stops being able to approve at once, even if still listed.
- **The requester never approves.** Thoth refuses an approver who is the user the action was requested
  for, the registered owner of the agent, or the creator of the API key that raised the hold. The
  raising key is recorded on the hold, so this holds whatever the key's scope (organization, fleet,
  endpoint or agent) and even if the key is revoked afterwards. For a hold raised before that record
  existed, Thoth refuses the creator of every active organization, fleet, endpoint and agent key. A hold
  raised by a signed-in session refuses that verified user; the user id named in the request body never
  stands in for it. If Thoth cannot tell who or what raised a hold (for example a legacy agent or tenant
  key), nobody can approve it.
  If the only person on the list is also the requester, the hold cannot be approved until a second person
  is listed. There is no bypass.
- **A signed-in person with a recent second factor.** Approving needs a signed-in session with recent
  MFA. An API key cannot approve, and an approver cannot be chosen by an API key either, so a leaked key
  cannot appoint an approver.
- **Fail closed.** If Thoth cannot read the list or cannot verify a person's membership, the approval is
  refused and the hold is unchanged.
- **Timing.** A change to the list applies to the next approval. The approval service caches the list for
  up to two seconds, so a removal can take that long to reach an approval already in flight.

Every change to the list is written to the workspace audit log with who made it and who was added or
removed.

## Read and change the list

Both routes need a signed-in organization administrator. Saving also needs recent MFA.

```http
GET /{tenant}/thoth/settings/approvers
```

```json
{
  "user_ids": ["user_01H..."],
  "updated_by": "user_01H...",
  "updated_at": "2026-11-12T10:00:00Z",
  "revision": 3
}
```

```http
PUT /{tenant}/thoth/settings/approvers
Content-Type: application/json

{ "revision": 3, "user_ids": ["user_01H...", "user_01J..."] }
```

`revision` is the value you read. If someone else saved in between, the request is refused with `409`
and you reload before saving. The body replaces the whole list; send `"user_ids": []` to clear it.
Refusals: `403` for an API key, a missing or stale second factor or a non-administrator; `422` for a
person who is not an active member of the organization; `400` for a duplicate, an empty entry, more than
50 entries or an unknown field.

To pick people, `GET /{tenant}/thoth/settings/approvers/candidates` lists the active organization
members (the same list the Slack reviewer picker uses).

## Set the list in the dashboard

Open **Settings → Approvers** (`/settings?section=approvers`) as an organization administrator.

- The page shows the approvers by name and email, the list's revision, and who last changed it and
  when. Each person's user ID is shown beneath their name. An approver whose details have not loaded
  yet is shown by user ID; **Load more members** brings in the next 100 members.
- Tick or untick members to choose the list (at most 50), then **Review change**. A confirmation says
  who is added and who is removed, and how many approvers there are before and after. Nothing is saved
  until you confirm.
- Removing the last approver, or saving an empty list, asks for a second, plainly worded
  confirmation: with no approver nobody can approve or deny a held action, and every hold ends in
  `BLOCK` at its deadline.
- Saving needs recent MFA. If yours is stale the dashboard asks you to confirm it and then retries the
  save once.
- If someone else saved while you were editing, the save is refused with "The approvers changed while
  you were editing", the current list is loaded again, and nothing is overwritten. If a person you
  chose is no longer an active, verified member, or Thoth cannot check membership with its identity
  provider, the page says so and nothing changes.
- Only organization administrators see the list; anyone else sees that an administrator chooses the
  approvers.
- A trial or self-serve workspace does not use this list: its workspace admins approve held actions in
  Approvals (or in Slack once connected), so the page says that instead of offering the list.

## Set the list with thothctl

Sign in as an organization administrator first (`thothctl auth login`); an API key is refused.

```bash
thothctl approvals approvers candidates          # active organization members and their user IDs
thothctl approvals approvers get                 # the list, its revision, who changed it and when
thothctl approvals approvers set --user-id user_01HABCDEF --user-id user_01HGHIJKL
thothctl approvals approvers set --user-ids user_01HABCDEF,user_01HGHIJKL
thothctl approvals approvers set --clear         # nobody can approve until a list is set
```

Every command takes `--json`. `set` replaces the whole list. It reads the current revision, then saves
against it, so if someone else saved in between it stops with "The approvers changed while this ran" and
overwrites nothing; run `get` and retry. `set` needs at least one `--user-id`, or `--clear` and nothing
else: an empty `set` is refused, so a mistake cannot empty the list. `--clear` prints a warning that
nobody can approve held actions until a list is set. If Thoth cannot check membership with its identity
provider, `set` stops with "Approvers could not be verified" and the list is unchanged. Saving needs
recent MFA, which `thothctl` asks you to confirm in the browser.

## Set the list with Terraform

```hcl
provider "thoth" {
  tenant_id            = var.tenant_id
  use_thothctl_session = true # run `thothctl auth login` first
}

resource "thoth_tenant_approvers" "this" {
  user_ids = ["user_01HABCDEF", "user_01HGHIJKL"]
}
```

`user_ids` are WorkOS user IDs, at most 50, each a verified, active member of your organization. The
set replaces the whole list. Reading the resource returns `revision`, `updated_by` and `updated_at`.

- **A signed-in administrator is required.** The provider must run as a signed-in admin
  (`use_thothctl_session = true` or an admin bearer token). With an organization API key the apply stops
  with an error that says so before it sends the change, because the API refuses keys here by design.
  Recent MFA is also required: sign in again with `thothctl auth login` if the apply is refused for it.
- **Concurrent changes are refused, not overwritten.** The resource reads the revision and saves
  against it. If someone else saved in between, the apply fails with "The approvers changed while this
  apply ran"; run the plan again.
- **Destroying the resource removes every approver.** It saves an empty list, and nobody can approve a
  held action until a new list is set. An empty `user_ids` does the same.
- **Import** with `terraform import thoth_tenant_approvers.this <tenant_id>`.

## Set the list from an MCP client

Connect with `thothctl mcp config` and sign in as an organization administrator (see
[Configure Thoth from an MCP client](https://docs.atensecurity.com/docs/mcp/configure-thoth)). The three tools are served only to a
signed-in administrator; an API-key session does not see them.

- `get_approvers` returns the list (user IDs and emails), its `revision`, who last changed it and
  when. It warns when the list is empty.
- `list_approver_candidates` lists the verified active members, 100 at a time, with their user IDs.
- `preview_approvers` takes `user_ids`, the complete new list (at most 50), and replaces the current
  one. The preview shows who is added and who is removed, with emails, and the revision it was
  computed from. Nothing changes until you call `commit_preview`, and the commit then needs the
  administrator to confirm in the browser with a recent second factor.

An empty `user_ids` is refused. To remove every approver, pass `clear: true`; the preview then says in
capitals that nobody can approve until a list is set, and warns when it would remove the last approver.

A preview is bound to the list it was made from. If anyone saves a different list before it is
committed, the commit is refused with `409` and nothing is overwritten; preview again.

## Set the list with Ask Thoth

On a workspace that uses the hosted assistant and has its own approvals, a signed-in administrator can
ask Ask Thoth who may approve, or to change the list ("make Dana and Sam the approvers"). Start a
whole-workspace conversation (no agents selected), because the list applies to every agent.

- Ask Thoth reads the list (`get_approvers`) and the members who can be added
  (`list_approver_candidates`), then proposes the same preview as the MCP tool `preview_approvers`: who
  is added and who is removed, the list it becomes, the revision it was computed from, and a warning
  when the list would be empty. It replaces the whole list, so it names everyone who should keep
  approving.
- Nothing changes until you confirm the preview card. The confirmation needs a recent second factor,
  and Thoth reads the list back afterwards before it says the change applied. If someone saved a
  different list in between, the confirmation is refused and nothing is overwritten; ask for a new
  preview.
- Ask Thoth chooses people by user ID from the member list. The assistant is shown member emails
  masked (for example `d***@example.com`) unless you wrote that email in the conversation; the cards
  in your browser show the full emails, read under your own access.
- Ask Thoth tells you when the list is empty, and removes every approver only when you plainly ask for
  it.
- It cannot confirm for you, and an API key cannot use it.
- A trial or self-serve workspace does not use this list, so Ask Thoth does not read or propose it
  there: it tells you that workspace admins approve held actions in Approvals (or in Slack once
  connected).

## When someone is refused

Approving through the dashboard or `thothctl approvals resolve` as a person who is not listed, or who
requested the hold, returns `403` with "You are not allowed to resolve this hold" and leaves the hold
unchanged. The hold still expires to `BLOCK` at its deadline.

A workspace with Slack connected keeps using its Slack reviewers for approvals made in Slack. This list
governs approvals made outside Slack.
