From 3dcc087246decdd1122777736d757b79b18b6c5e Mon Sep 17 00:00:00 2001
From: "@mrubens" <2600+mrubens@users.noreply.github.com>
Date: Sat, 3 Oct 2026 03:12:11 +0000
Subject: [PATCH] docs: explain policy changes for running tasks

---
 apps/docs/integrations/index.mdx | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/apps/docs/integrations/index.mdx b/apps/docs/integrations/index.mdx
index ac9f6e9487..4460c19d81 100644
--- a/apps/docs/integrations/index.mdx
+++ b/apps/docs/integrations/index.mdx
@@ -77,12 +77,13 @@ Experimental opt-in:
 
 Tools are grouped into read-only and write/delete tools when the integration
 describes them, and each group can be set in one click. Choices apply to the
-whole deployment from the next session turn. In a session, the owner can also
-ask to be asked about any tool for the rest of that session from the tool's
-call in the transcript. When an approval is pending, it can be decided from the
-session; Slack, Discord, and Telegram also show approval buttons in the
-conversation. Microsoft Teams keeps the approval action in the linked web
-session.
+whole deployment. If a tool's policy changes while a task is already running,
+the task follows the new choice at its next call without needing a restart. In
+a session, the owner can also ask to be asked about any tool for the rest of
+that session from the tool's call in the transcript. When an approval is
+pending, it can be decided from the session; Slack, Discord, and Telegram also
+show approval buttons in the conversation. Microsoft Teams keeps the approval
+action in the linked web session.
 
 Members manage the same choices for their own private MCP servers from
 [Personal Settings](/personal-settings); those apply to their own sessions