Evose
GovernSecurity

Resource Policy ACL

Org-level resource access rules · RBAC / Policy / ACL three-layer stack

Resource policies are org-level global rules that complement RBAC and workspace ACL, handling complex cross-workspace scenarios.

Three-Layer Stack

1. Org RBAC (roles)             → Can I enter this workspace?
2. Resource policy (global)     → Cross-workspace access rules
3. Workspace ACL (per-resource) → Can I use this Agent?

If any layer denies → denied.

Policy Subjects

SubjectExample
UserAlice
Role"Finance audit"
Department"Marketing"

Policy Objects

ObjectExample
Agent / Workflow / ChatflowOne or many
Knowledge base / Data sourceOne or many
Tool / Skill / ModelOne, or grouped by type
CredentialA specific credential

Policy Actions

ActionDescription
ViewSee the resource exists
UseCall / trigger
EditModify
Manage+ ACL management / delete

When to Use Resource Policy vs Workspace ACL

ScenarioUse
"Marketing dept read-only on all org KBs"Resource policy (cross-workspace)
"Agent X usable only by user_a / user_b"Workspace ACL (single resource)
"New-hire role can't use any production tool"Resource policy (across tool types)
"Finance can't edit any R&D workspace resource"Resource policy (cross-workspace)

A Composite Example

Policy name: Finance org-wide read-only
Subject: Department = Finance
Object: All org Agent / Workflow / KB
Actions: View + observe only — no use / edit / manage

→ Even after Alice (Finance) joins the Marketing workspace, she can only view.

Coordination with RBAC

"Finance Audit" role's system permissions: observe + reports

Resource policy "Finance org-wide read-only": view-only across all spaces

Workspace X ACL: Agent A explicitly denies Alice → Alice can't see it

Final experience for Alice in Workspace X: all resources visible except Agent A.

Anti-Patterns

  • Using a resource policy to substitute workspace ACL — single-resource concerns belong in the workspace
  • Overly complex policies (5 nested conditions) — split into multiple simple policies, easier to audit
  • Not maintaining a policy-change log — query in audit logs

Next Steps

On this page