Change the access policy
Set defaults or target specific requests, then review JSON and contradictions.
Set workspace defaults
Open Policies → Defaults & JSON → Edit defaults. Choose the default access and write decision, review the scope and publish. Publishing a policy version invalidates earlier exact approvals.
Define a targeted rule
Select Add policy and name the rule. Choose its enforcement and the conditions that identify the intended requests.
- Select connections, tools, principals or teams. Search accepts approximate names; enforcement uses the exact selections.
- Use explicit prefixes where offered, such as a resource folder. Multiple request conditions must all match.
- Team selections follow current membership, including people who join later. Use the team’s Policy page to inspect its defaults and conditional rules.
Review before publishing
Select Review policy. Inspect the generated JSON and contradiction results, then test representative requests against the draft. Resolve validation errors and check warnings before publishing. An allow rule cannot override required checks, workspace denials or stricter team restrictions.
Inspect current policies
Applied shows built-in controls, custom rules and group policies. Filter by user, group or connection. Use each row’s action menu to view, edit, disable or restore a policy where supported. Needs review highlights contradictions, outdated targets and rules with no effect.
Investigate enforcement
Use Policy checks for issue details and Enforcement for the latest retained blocked, approval-required or uncertain result. Compare its recorded policy with current settings; authorization and upstream completion are separate.
Frequently asked questions
Can a team policy weaken an organization denial?
No. Organization restrictions remain in force. For matching rules, deny takes precedence over approval, then allow.