A human-in-the-loop control you have not located precisely is not a control. It is a belief about a control.
Updated November 12, 2026: In a Slack channel, as in a Slack DM, posting a Slack message is the only action that waits for approval; this post no longer says a channel also holds back anything Insulin can’t recognize as a read.
Insulin can pause before a sensitive tool call and ask. A Tool Approval Required card appears in the thread, naming the tool, showing the arguments it would be called with, and explaining why it stopped. Allow runs it; Deny does not. Afterwards the card keeps a badge recording what you chose.
Leave it alone and the request times out after about three minutes, the card is marked Expired, and nothing is sent. That default matters: an unanswered approval fails closed.
The part that decides how you design around it
The card is offered in an interactive solo chat in the web workspace, on the main thread, and in Slack: a DM with Insulin, or a channel where you @mentioned it. It is not offered — and the action is not held back — in:
- an Insulin channel,
- a Microsoft Teams DM,
- a reply written inside a sub-thread in the web workspace,
- a job run.
Those surfaces cannot render the card or send your decision back, so the turn proceeds without pausing. A goal’s background rounds cannot show it either, so they do not get the Slack send tool at all: a goal never posts to Slack on its own.
This is worth reading twice, because the intuitive assumption is the opposite. Most people assume an approval requirement is a property of the tool — arm it once, and it holds everywhere the tool can be called. Here it is a property of the surface: the same agent calling the same tool pauses in one place and proceeds in another.
What the card covers, though, is the same wherever it is offered: posting a message to Slack waits for it, since other people can read the message the moment it is sent. In a Slack channel where you @mentioned Insulin, as in a DM, that is the only action that waits. Creating or changing a record, a memory, a job, an agent or a channel, and handing part of the work to a helper agent, don’t wait; what bounds them is the access you gave each connection and your own Fours permissions.
What to do with that
Scope the agent, not the prompt. If an action genuinely must not happen without a human, the control is the agent’s integration allowlist — what it can reach at all, and whether each integration is Read-only, Edit or Full — rather than an approval card that only some surfaces can show. An agent that cannot call the tool cannot call it in an Insulin channel or a job run either.
Decide deliberately which agents belong in Insulin channels. A channel is a collaboration surface, and an agent that only ever reads and drafts is a good fit for one. An agent that writes to a business system is a different proposition there, because nothing in an Insulin channel waits on the approval card, not even a post to Slack.
Treat the card as a guardrail on the surfaces that can show it, which is exactly how the documentation frames it — not as a workspace-wide guarantee that every sensitive action will wait for you.
Frequently asked questions
Does the tool approval card appear everywhere?
No. It is offered in an interactive solo chat on the web workspace’s main thread, and in Slack: a DM with Insulin or a channel where you @mentioned it. In an Insulin channel, a Teams DM, a web sub-thread or a job run, the action proceeds.
What happens if I ignore an approval request?
It times out after about three minutes, the card is marked Expired, and nothing is sent. An unanswered approval fails closed.
How do I stop an agent acting without approval in an Insulin channel?
Scope the agent rather than relying on the card. Restrict which integrations it can reach, or set them to Read-only, so the action is impossible rather than merely gated on a surface that cannot show the gate.
Does the card record what I decided?
Yes. After you answer, the card keeps a badge showing Approved or Rejected, and an unanswered one is marked Expired.
Takeaways
- The approval card is offered in the web workspace and Slack: interactive solo chat on the main thread, a DM with Insulin, or a channel where you @mentioned it.
- Insulin channels, Teams DMs, web sub-threads and job runs do not pause — they proceed.
- In a Slack channel, as in a DM, only posting a Slack message waits for the card; creating or changing a record doesn’t, so each connection’s access level is what bounds it.
- Approval is a property of the surface, not of the tool. That is the counterintuitive part.
- An unanswered request expires after ~3 minutes and nothing is sent.
- If an action must never happen unapproved, restrict the integration instead.
More on the practice in human approval for AI agents, on scoping in agents, and on shared threads in how channels work.
Sources
Primary sources for the platform rules cited above. Last verified November 12, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.
- Fours docs: Agents — Tool Approvals — Posting a message to Slack as the call that pauses for approval, whether asked in the web workspace, a Slack DM or a Slack channel; where the card is and is not offered; a goal's background rounds without the Slack send tool; the three-minute expiry; What Insulin can do when mentioned in a channel: creating or changing a record, a memory, a job, an agent or a channel, and handing work to a helper agent, not waiting, bounded by each connection's access and your own Fours permissions; and each integration set to Read-only, Edit or Full
Keep reading
Stay Updated
New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.
Follow Fours on LinkedIn