From c7dd9b92dbf6dab9378701391474bf4c1a11ba7b Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Mon, 7 Sep 2026 08:23:15 +0000 Subject: [PATCH] docs: explain unresolved governance status Governance monitoring did not explain the unresolved state shown when Docker cannot select one governing organization. Document the multiple-organization trigger, fail-closed behavior, and administrator escalation. Co-Authored-By: Codex --- .../governance/monitor-and-enforce/monitoring.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/manuals/ai/sandboxes/governance/monitor-and-enforce/monitoring.md b/content/manuals/ai/sandboxes/governance/monitor-and-enforce/monitoring.md index 8f2333ce8b5..70054518722 100644 --- a/content/manuals/ai/sandboxes/governance/monitor-and-enforce/monitoring.md +++ b/content/manuals/ai/sandboxes/governance/monitor-and-enforce/monitoring.md @@ -69,6 +69,14 @@ stale timestamp, the daemon may not have the most recent org policy. Run `sbx policy reset` to force a fresh pull. `Hidden` reports how many inactive rules are suppressed and how to reveal them. +If Docker can't determine which organization governs your account, policy +output shows `Governance: Unresolved`, and the dashboard shows the same +unresolved state. For example, this happens when your account belongs to +multiple organizations with governance enabled. Policy enforcement fails closed +until the conflict is resolved, so local allow rules can't grant access. Contact +an administrator for the affected organizations to resolve the conflicting +governance configuration. + ### Showing inactive rules When organization governance is active, local and kit-defined allow rules are