diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md
index caebe377..ef65b09f 100644
--- a/docs/web-ui/dashboard.md
+++ b/docs/web-ui/dashboard.md
@@ -384,17 +384,27 @@ headers tilt -45° via CSS so each column reads as a narrow
   re-adding goes through the edit form's targets multi-select)
 - **not a target** → empty cell
 
-Per-schedule action column: a `↯ fire now` button sends an
-out-of-band manual pulse to every active target (recurring
-schedules keep their cadence; one-shots are consumed after
-the manual fire), an `✎ edit` button expands an inline edit
-form as a colspan'd row directly under the schedule's row
-(body / description / interval / next-fire / targets all
-editable; targets are a multi-select diff'd against the
-original active set so unchecked-was-active = `targets_remove`,
-checked-not-originally-active = `targets_add`; submit PATCHes
-`/api/schedules/{id}`), and a `✕` button cancels the whole
-schedule (`POST /api/schedules/{id}/cancel`).
+Per-schedule action column:
+
+- **`↯ fire now`** — sends an out-of-band manual pulse to every
+  active target (recurring schedules keep their cadence; one-shots
+  are consumed after the manual fire). Disabled for paused schedules.
+- **`⏸` / `▶` pause/resume toggle** — only on recurring schedules
+  (one-shots may also be paused to delay a one-time fire, so the
+  button always appears). Paused rows show a `⏸ paused` badge in the
+  `next` column and are sorted to the middle bucket (after active,
+  before cancelled). A paused schedule does not fire regardless of
+  `next_fire_at`; resuming (`▶`) clears the pause without adjusting
+  the next-fire time. POSTs to `/api/schedules/{id}/pause` or
+  `/api/schedules/{id}/resume`.
+- **`✎ edit`** — expands an inline edit form as a colspan'd row
+  directly under the schedule's row (body / description / interval /
+  next-fire / targets all editable; targets are a multi-select diff'd
+  against the original active set so unchecked-was-active =
+  `targets_remove`, checked-not-originally-active = `targets_add`;
+  submit PATCHes `/api/schedules/{id}`).
+- **`✕`** — cancels the whole schedule
+  (`POST /api/schedules/{id}/cancel`).
 
 The `next` column cell (`.sched-due`) carries a `data-due-at`
 Unix timestamp attribute; a shared 1s ticker rewrites it