Policy Bindings
Policy bindings attach content policy profiles and related governance controls to the traffic where they should apply.
Bindings are the placement layer for governance. Profiles define what to detect or enforce; bindings decide where those profiles are active.
Binding Targets
Bindings can scope policy to:
| Target | Example |
|---|---|
| Organization | Apply to all governed traffic in an organization. |
| User | Apply to one authenticated user. |
| Agent | Apply to one owned agent identity. |
| Auth group | Apply to an OIDC, Okta, SCIM, or imported group. |
| Gateway key | Apply to one model gateway key. |
| Endpoint | Apply when a request targets a specific endpoint. |
| Model route | Apply to selected route or model traffic. |
| Work metadata | Apply when request metadata matches a configured workflow, business unit, or environment. |
API Surface
GET /api/v1/llm/policy_bindings
PUT /api/v1/llm/policy_bindings
GET /api/v1/llm/policy_bindings/{binding_uuid}
DELETE /api/v1/llm/policy_bindings/{binding_uuid}Evaluation
Bindings are additive. Eden collects all matching bindings for the request context, evaluates the associated policies, and enforces the strictest applicable action before provider, template, or tool egress.
Binding Strategy
Use broad bindings for organization-wide requirements and narrow bindings for riskier contexts:
| Strategy | Example |
|---|---|
| Organization baseline | Audit credential terms and payment instructions everywhere. |
| Group-specific policy | Apply research restrictions to a fund, desk, project group, or claims team. |
| Route-specific policy | Require stricter checks on tool-calling, high-capability models, or external routes. |
| Endpoint-specific policy | Add masking or block rules when a request can reach sensitive systems. |
| Metadata-specific policy | Activate policy only for a workflow, business unit, region, customer segment, or environment. |
Change Management
Policy bindings should be versioned and reviewed like other enforcement configuration. A rollout usually starts with audit or simulation, then moves to redaction or blocking once operators confirm the match rate. Keep binding names business-readable so dashboards, approvals, and exports explain why a policy applied.
Telemetry
Binding telemetry records binding identifiers, profile identifiers, target type, status, and counts. It does not need raw prompts or raw matched values to prove that a policy applied.