Background
The current PolicyView is powerful but intimidating for non-engineers. It requires raw CEL authoring and lacks visibility into where bundles are currently being used across the system.
Goals
- Usage Visibility: Display which integrations (agents) are actively referencing a policy bundle. Implement a safeguard/warning modal when attempting to delete a bundle that is currently in use.
- Rule Templates: Introduce a template mode in the
PolicyRuleEditor. This allows users to create common rules (e.g., 'Require approval for bash', 'Deny prompt injection') via simple forms, automatically generating the underlying CEL expression.
Dependencies
Requires the backend API updates from Design 01 to expose policy_bundle_ids within the IntegrationDefinition payload.
Based on: design-03-policy-library-ui.md
Background
The current
PolicyViewis powerful but intimidating for non-engineers. It requires raw CEL authoring and lacks visibility into where bundles are currently being used across the system.Goals
PolicyRuleEditor. This allows users to create common rules (e.g., 'Require approval for bash', 'Deny prompt injection') via simple forms, automatically generating the underlying CEL expression.Dependencies
Requires the backend API updates from Design 01 to expose
policy_bundle_idswithin theIntegrationDefinitionpayload.Based on:
design-03-policy-library-ui.md