From 420684e0e95792240095d0b7aa35c07af541d036 Mon Sep 17 00:00:00 2001 From: Mohamed Makhlouf Date: Sat, 7 Nov 2026 04:57:11 +0300 Subject: [PATCH] docs: clarify policy change timing in organization overview Clarify that the 5-minute sync is the only distribution delay, and that when changes apply after syncing depends on the evaluation point (per-request for network/MCP vs. sandbox startup for filesystem). Fixes #26555 Signed-off-by: Mohamed Makhlouf --- .../manuals/ai/governance/organization/policies/_index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/manuals/ai/governance/organization/policies/_index.md b/content/manuals/ai/governance/organization/policies/_index.md index 0ede956a4ed..bed18f3c0c3 100644 --- a/content/manuals/ai/governance/organization/policies/_index.md +++ b/content/manuals/ai/governance/organization/policies/_index.md @@ -130,8 +130,10 @@ access, so it stays active. ## When policy changes reach developers -Policy changes reach developer machines within 5 minutes. When a synced change -takes effect also depends on the policy type. For more details, see +Policy changes reach developer machines within 5 minutes. Once synced, when the +change applies depends on the policy type: network and MCP policies apply to +subsequent requests, while filesystem policies apply when a sandbox starts. For +more details, see [Organization network access policies](network.md#when-changes-take-effect), [Organization filesystem access policies](filesystem.md#when-changes-take-effect), and [Organization MCP access policies](mcp.md#when-changes-take-effect).