docs: notify people, groups and Slack channels about scheduled task runs (CUB-5670)

docs-mintlify/docs/explore-analyze/scheduled-tasks.mdx

@@ -41,10 +41,11 @@ searchable. Each row shows:
   under it, in your timezone and naming it. It reads "Paused" for a paused
   task, "Manual" for a manual one, and "Not scheduled" for an enabled task
   that has no next run.
-- **Notifications** — "Inbox" when the task notifies its creator in the
-  [inbox](/docs/inbox) (see
-  [Getting notified when a run finishes](#getting-notified-when-a-run-finishes)),
-  otherwise "—".
+- **Notifications** — where the task's notifications go (see
+  [Notifying people when a run finishes](#notifying-people-when-a-run-finishes)):
+  its channels, how many people and groups, and its Slack channels, for
+  example "Inbox, Email · 3 people, 1 group · #sales, #finance-alerts", or
+  "Nobody is notified".
 - **Last check** — on a conditional task, the outcome of its last check, for
   example "3 minutes ago, Count increased by 2.7%, notified", or "Not checked
   yet" before the first one; "—" on a task with no condition. Only the task's
@@ -78,9 +79,9 @@ A task has:
   task created from chat keeps that chat's agent.
 - **Schedule** — how often the task runs (see below).
 - **Enabled** — a toggle to activate or pause a scheduled task.
-- **Notify me when a run finishes** — a toggle to get an
-  [inbox](/docs/inbox) notification after each run (see
-  [Getting notified when a run finishes](#getting-notified-when-a-run-finishes)).
+- **Notify** — the people and groups to notify when a run finishes, and how:
+  **Inbox**, **Email**, and **Slack** channels, in any combination (see
+  [Notifying people when a run finishes](#notifying-people-when-a-run-finishes)).
 - **Notify only when a condition is met** (optional) — a metric condition
   that decides whether the agent runs at all (see
   [Conditional tasks](#conditional-tasks)).
@@ -141,14 +142,23 @@ The task notifies once each time the condition starts to hold:
 - The agent runs the task's **Instructions** in a new chat thread that opens
   with the facts it found: the value read, what it was compared with, and the
   periods. Ask follow-up questions in that thread as in any chat.
-- If the task's
-  [Notify me when a run finishes](#getting-notified-when-a-run-finishes)
-  toggle is on, your in-app inbox gets a message titled with the task's name
-  and *"condition met"* that states the change, for example *"Revenue rose
-  7.2 % (Aug → Sep 2026), above your 5 % threshold"*. The message names the
-  measure by the title picked in the task dialog, or by its full name (such
-  as `orders.revenue`) on a task that has no title for it. With the toggle
-  off, the agent still writes the thread, but nothing reaches your inbox.
+- The task's [recipients](#notifying-people-when-a-run-finishes) are
+  notified on the channels the task has on. The creator's message is titled
+  with the task's name and *"condition met"* and states the change, for
+  example *"Revenue rose 7.2 % (Aug → Sep 2026), above your 5 % threshold"*.
+  The message names the measure by the title picked in the task dialog, or by
+  its full name (such as `orders.revenue`) on a task that has no title for
+  it. Everyone else, and each Slack channel, is told that the condition
+  started to hold, without the figures. The figures stay in the run's chat
+  thread, which everyone the task is shared with can open (see
+  [Managing tasks](#managing-tasks)).
+
+A task with a condition must notify someone: **Inbox** or **Email** on with at
+least one person or group picked, or **Slack** on with at least one channel.
+Until it does, the dialog's **Create** (or, when editing, **Update**) button
+stays disabled and says why, and the agent refuses the save. The Platform API
+refuses it too when the request sets the task's `notification` field; a request
+that leaves that field out is saved.
 
 While the condition keeps holding, later checks send nothing. Once a check
 finds it no longer holding, the next time it holds notifies again. Changing
@@ -209,9 +219,9 @@ That exception carries the creator's data access with it: an admin or a
 **Manage all scheduled tasks** holder who edits another user's task changes what runs under that user's access. A run's chat
 thread belongs to the task's creator, and only the creator, admins, users with
 the **Access chat history**
-[permission](/admin/users-and-permissions/custom-roles), and people the thread
-itself is shared with can open it. Sharing the task doesn't share its runs'
-chat threads.
+[permission](/admin/users-and-permissions/custom-roles), people the thread
+itself is shared with, and the people and groups the task is shared with can
+open it. For anyone the task is shared with, the thread is view-only.
 
 From the list, you can:
 
@@ -263,6 +273,8 @@ The page shows:
 - **Instructions** — the task's prompt.
 - **Repeats** — the schedule with its timezone, for example "Daily at 9:00
   AM UTC".
+- **Notifies** — where the task's notifications go, as in the list's
+  **Notifications** column.
 - **Condition** — on a conditional task only, after **Instructions** and
   **Repeats**: the condition in plain language (for example, *"When Count
   changes by ≥ 5 % vs the previous month"*), then, on a line of its own,
@@ -277,8 +289,9 @@ The **Last check** shows when the last check ran, its result (**Condition not
 met**, **Condition met — notified**, **Still holding — already notified**,
 **Could not check**, or **Check failed**), the value it read with the
 comparison it made, and, when nothing was sent, why. On a task that notifies
-nobody when its condition holds, for example because **Notify me when a run
-finishes** is off, the two results of a check that finds it holding read
+nobody when its condition holds, for example one created through the Platform
+API without a `notification` field, the two results of a check that finds it
+holding read
 **Condition met** and **Still holding**. While a check runs, it reads
 **Checking…**. After a check that finds the condition starting to hold, the
 agent run it started appears in **History** on the same page. The check reads
@@ -308,22 +321,64 @@ run.
 The task runs headlessly under the security context of the user who created
 it, so it sees exactly the data that user can access.
 
-### Getting notified when a run finishes
-
-Turn on **Notify me when a run finishes** in the task's create or edit dialog
-to get an [inbox](/docs/inbox) notification when a run finishes or fails. The
-toggle is on by default for a task that you create in the dialog. It applies
-to both scheduled runs and **Run now**. On a
-[conditional task](#conditional-tasks), a check that runs no agent sends
-nothing.
-
-The notification goes to the task's creator, even when an admin or another user
-with **Manage all scheduled tasks** edits or runs the task. See [Inbox](/docs/inbox#notification-types) for what it shows.
-
-A task that you create with the agent or the Platform API has notifications
-off, unless you ask for them: for example, *"schedule a daily summary of
-yesterday's signups at 9am and notify me when it runs."* With the Platform
-API, set `notificationEnabled` to `true`.
+### Notifying people when a run finishes
+
+The **Notify** section of the task's create or edit dialog decides who hears
+about a finished run, and how:
+
+- **People and groups** — any workspace users and user groups, picked from
+  the same search as the **Share** dialog. A group is expanded to its members
+  when the run finishes, so people who join it later are notified too. A
+  person picked directly and through a group is notified once.
+- **Send by** — **Inbox** (an [inbox](/docs/inbox) notification), **Email**,
+  and **Slack**, in any combination. **Inbox** and **Email** go to every
+  person and group picked above. With **Slack** on, pick one or more
+  channels: each gets one post. If Slack isn't connected to the workspace,
+  the dialog offers to connect it. **Inbox** is unavailable when the inbox is
+  off for the workspace, and a task saved with it on then sends no inbox
+  notifications but still sends its other channels.
+
+A new task starts with you picked and **Inbox** on, so it notifies you the way
+it did before; you can remove yourself. With every channel off, nobody is
+notified, and the dialog says so.
+
+Each notification carries the task name, whether the run succeeded, the start
+of the agent's answer, and a link that opens the run. Each Slack post carries
+the same answer and link. Saving a task with a newly picked person or group
+shares the task with them, view-only, so the link opens the run for them,
+whether they were picked in the dialog, by the agent, or through the Platform
+API. Removing them from **Notify** leaves the share in place; remove it in the
+**Share** dialog. Besides the creator, a run notifies only people who can open
+the task (admins, and anyone it's shared with directly, through a group, or
+with the whole organization) and read its deployment. A picked person fails
+that in two ways: their share was removed in the **Share** dialog after they
+were picked (saving the task again doesn't share it back; remove them from
+**Notify** and pick them again), or they can't read the deployment. The run
+skips them, and the dialog marks them **Not shared: won't be notified** in
+both cases. Deactivated users and people outside the workspace get nothing.
+
+Notifications go to the task's recipients, whoever runs the task: an admin or
+a user with **Manage all scheduled tasks** who edits or runs it is notified
+only if they are a recipient.
+
+Each task email has an unsubscribe link. Unsubscribing stops that person's
+emails from this task, scheduled runs included, until the task's creator picks
+them again directly.
+
+A failed run notifies only the task's creator, if they are among the task's
+recipients, on the task's **Inbox** and **Email** channels; other recipients
+and Slack channels get nothing. Notifications apply to both scheduled runs and
+**Run now**. On a [conditional task](#conditional-tasks), a check that runs no
+agent sends nothing. See [Inbox](/docs/inbox#notification-types) for what an
+inbox notification shows.
+
+A task that you create with the agent or the Platform API notifies nobody,
+unless you ask for it: for example, *"every Monday summarize sales, email it
+to the Finance group and anna@example.com, and post it in #sales."* The agent
+names people by email and groups by name. Channels belong to the whole task,
+as in the dialog: asking the agent to notify one more person by inbox turns
+**Inbox** on for everyone the task notifies, and the agent tells you so. With
+the Platform API, set the task's `notification` field.
 
 ### What the agent can do in a scheduled run
 
@@ -365,7 +420,7 @@ task"*.
 
 The agent manages task definitions: when listing tasks, it can report each
 task's id, name, description, schedule, timezone, enabled state, next run
-time, **Notify me when a run finishes** setting, and condition with its last
+time, who it notifies and how, and condition with its last
 check (the check's values and error text only to the task's creator). It can
 also add, change, or remove a task's [condition](#conditional-tasks) — for
 example, *"tell me when monthly orders change by 5% or more."* A task's run
@@ -380,7 +435,14 @@ scripts and CI with the [Platform API](/api-reference/introduction) (by
 default, only admins can
 [create API keys](/admin/account-billing/api-keys#personal-api-keys)). Its
 Scheduled Tasks endpoints follow the same [limits](#limits) and
-[permissions](#managing-tasks) as the **Scheduled** page. A task's optional
+[permissions](#managing-tasks) as the **Scheduled** page. A task's
+`notification` field holds its
+[recipients and channels](#notifying-people-when-a-run-finishes): `channels`
+(`inbox`, `email`, `slack`), `userIds`, `groupIds`, and `slackChannels`, with
+at most 1,000 users, 200 groups, and 50 Slack channels. An unknown user or
+group id is refused. The older `notificationEnabled` field is
+deprecated: it reads whether the creator gets an inbox notification, and
+writing it adds or removes that. A task's optional
 `condition` field holds its [condition](#conditional-tasks) (`null` on an
 update removes it), and `lastConditionCheck` holds its latest check, whose
 values and error text are returned only to the task's creator. See the

docs-mintlify/docs/inbox.mdx

@@ -40,7 +40,7 @@ New notifications appear as they arrive. You don't need to reload the page.
 | Mention | Someone mentions you in a [dashboard comment][ref-comments], or edits a comment to add a mention of you | Each mentioned user, except the author | The comment on the dashboard |
 | Alert | An [alert][ref-alerts] fires or resolves | Recipients of the alert who are Cube users | The deployment's **Status** page |
 | Budget | Usage crosses a [budget][ref-budgets] threshold | Users who get the budget's notifications and have a Cube account | No **Open** button |
-| Scheduled task run | A run of a [scheduled task][ref-scheduled-tasks] finishes or fails, if the task has [notifications][ref-scheduled-task-notifications] on | The task's creator | The run's chat thread. If the run failed before it started a thread, the task's page. |
+| Scheduled task run | A run of a [scheduled task][ref-scheduled-tasks] finishes or fails, if the task notifies by **Inbox** | The task's [recipients][ref-scheduled-task-notifications] who can view the task and read its deployment. For a failed run, only its creator, if they are a recipient | The run's chat thread. If the run failed before it started a thread, the task's page. |
 | New Cube version | A deployment runs an older version than the latest one on its [update channel][ref-update-channels] | Admins | The deployment's **Settings** page |
 | End of support | A deployment runs a Cube version that is about to reach end of support. You get one notification with each end-of-support email. | Admins | The deployment's **Settings** page |
 | Production build failed | A build of a deployment's production branch fails | The user who started the build. If no user started it, for example a Git push, or that user is deactivated: admins | The build and its logs |
@@ -60,11 +60,13 @@ example when the run only built a chart, it shows how the run started and how
 long it took. For a failed run, it shows the error. For a run that a
 [conditional task's][ref-conditional-tasks] condition started, the title reads
 **Daily signups: condition met**, and it shows the change the check found
-instead of the answer.
+instead of the answer. Only the creator's notification shows the figures;
+everyone else's says that the condition started to hold.
 
 The inbox does not send notifications by email or Slack. Alerts and budgets send
 their own email, as set up on the alert or budget, and end-of-support notices
-come with their own email, as do dashboard review notifications. A Google Sheets
+come with their own email, as do dashboard review notifications. A scheduled
+task can also notify by email or Slack, as set up on the task. A Google Sheets
 delivery can also notify its owner by email or Slack, and emails admins while
 the owner's Google account can't open the spreadsheet.
 
@@ -97,7 +99,7 @@ Cube asks you to confirm both actions. You can't undo a delete.
 [ref-alerts]: /admin/monitoring/alerts
 [ref-budgets]: /admin/account-billing/budgets
 [ref-scheduled-tasks]: /docs/explore-analyze/scheduled-tasks
-[ref-scheduled-task-notifications]: /docs/explore-analyze/scheduled-tasks#getting-notified-when-a-run-finishes
+[ref-scheduled-task-notifications]: /docs/explore-analyze/scheduled-tasks#notifying-people-when-a-run-finishes
 [ref-conditional-tasks]: /docs/explore-analyze/scheduled-tasks#conditional-tasks
 [ref-update-channels]: /admin/deployment#update-channels
 [ref-scheduled-refreshes]: /docs/explore-analyze/scheduled-refreshes