Skip to content

docs: clarify policy change timing in organization overview #26558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Mhdomer wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −2
Open

docs: clarify policy change timing in organization overview #26558

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/manuals/ai/governance/organization/policies/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
Loading