AI Governance Survey
All controls default to the recommended secure posture. BLOCK = control applied. ALLOW = risk accepted — the behavior is permitted. Toggle each control based on your organization's risk tolerance.
Claude Desktop/Cowork
Web & desktop collaboration interface
Do you want every user in the organization to have unrestricted access to Claude Cowork without any admin-level gating?
Control Applied
Toggle Cowork OFF organization-wide in Admin Settings > Capabilities (or use Enterprise RBAC custom roles to limit Cowork access).
Do you want developers to freely use Claude Cowork with full Chrome integration and unrestricted web search?
Control Applied
Disable the Claude-in-Chrome bridge + set org-wide web-search restrictions / site allowlists in Admin Settings > Connectors.
Do you want users to install or connect arbitrary MCP servers / plugins in Claude Cowork?
Control Applied
Deploy managed-mcp.json allowlist via MDM (Jamf/Intune) so only org-approved MCPs can be used.
Do you want Claude Cowork to run scheduled/background tasks or Dispatch without oversight?
Control Applied
Disable Dispatch toggle (Admin Settings > Capabilities) and enforce folder-scoping / mount-point restrictions.
Do you want full visibility into Cowork activity (including prompts, MCP calls, and skills)?
Control Applied
Enable OpenTelemetry streaming and configure log inclusion for prompts/MCP/skills (default excludes them).
Claude CLI
Claude Code terminal interface
Do you want developers to bypass all permission prompts in the Claude CLI (Claude Code terminal interface)?
Control Applied
Set "disableBypassPermissionsMode": "disable" + "allowManagedPermissionRulesOnly": true in managed-settings.json.
Do you want unrestricted Bash, file read/write, or network commands in the CLI?
Control Applied
Add explicit deny/ask rules in managed-settings.json (e.g., deny "Bash(curl *)", "Read(**/.env)", "Write(**)" with ask).
Do you want users to run custom hooks or non-managed hooks in Claude CLI?
Control Applied
Set "allowManagedHooksOnly": true in managed-settings.json.
Claude Code in Web Browser
Cloud-hosted coding sandboxes
Do you want Claude Code (web) sessions to have unrestricted network access in the cloud sandbox?
Control Applied
Force "No network access" or custom restricted-domain environment (default allowlist is broad).
Do you want developers to run Claude Code web with full filesystem and credential exposure risk?
Control Applied
Use the isolated cloud sandbox + enforce no sensitive credentials in the session (proxy handles git auth).
Claude in Chrome
Browser extension for page interaction
Do you want the Claude Chrome extension enabled for anyone in the organization?
Control Applied
Toggle the extension OFF org-wide in Admin Settings > Capabilities (or use site blocklist).
Do you want Claude in Chrome to interact with any website without restriction?
Control Applied
Configure site allowlist + blocklist in admin console (Team/Enterprise only).
Do you want autonomous (hands-off) mode in Claude in Chrome?
Control Applied
Force default "Ask Before Acting" mode; disable pre-approve for high-risk actions (purchases, deletes).
Codex Desktop
Computer-use desktop agent
Do you want Codex Desktop to have unrestricted computer-use (screen/keyboard/mouse control) without approvals?
Control Applied
Enforce approval_policy in config.toml + require macOS TCC prompts (Screen Recording + Accessibility) per-session.
Do you want Codex Desktop plugins or 90+ marketplace extensions installed without vetting?
Control Applied
Restrict to private/approved marketplace only via team config.toml.
Do you want Codex Desktop to store credentials or run with full session privileges?
Control Applied
Set sandbox_mode to :read-only or :workspace and protect writable roots in config.toml.
Codex CLI
Command-line coding agent
Do you want Codex CLI to auto-execute without approval (full access mode) on developer machines?
Control Applied
Force approval modes: read-only or auto (with explicit workspace boundaries) in config.toml layers.
Do you want Codex CLI to trust and auto-load MCP servers from project-local config files?
Control Applied
Disable project config loading for untrusted repos or enforce system-level MCP allowlist only.
Do you want Codex CLI to have unrestricted network or filesystem access outside the workspace?
Control Applied
Set sandbox_workspace_write.* protected paths + network allowlist in config.toml.
Do you want Codex CLI to override environment variables or CODEX_HOME from project .env files?
Control Applied
Lock cli_auth_credentials_store and prevent CODEX_HOME redirection via managed config.
20 controls will be enforced in your deployment.
Ready to generate your policy and receive your governance package?