Skip to main content

Policies

Use Policies to enforce best practices and reduce incidents across your automations.

Overview​

  • Policies evaluate scenarios/blueprints against guardrails you define.
  • Severities help prioritize remediation (e.g., critical, warning, info).
  • Policy state can be enabled/disabled; changes affect future validations.

Common policy types (examples)

  • Reliability: timeouts, error handling, retries configured
  • Secrets & PII: usage of secure stores, no hardcoded secrets
  • Performance: rate limits, batching, pagination

Prerequisites​

  • At least one imported or uploaded scenario/blueprint.

Create a Policy​

  1. Open Policies from the sidebar.
  2. Click New Policy.
  3. Choose a policy type and set the scope/thresholds.
  4. Set severity and save.

Policies list (placeholder)

Edit or Disable a Policy​

  1. From the policy list, select a policy.
  2. Adjust thresholds, scope, or severity.
  3. Save changes or toggle to disable.

Create from a Template​

  1. Open Templates.
  2. Pick a policy template and click Use Template.
  3. Customize fields and save.

See Policy Effects​

  • Run Validate on a scenario to see findings tied to active policies.
  • Alerts may reference policy‑related violations depending on configuration.

Tips​

  • Start with medium severity to avoid alert noise; raise severity after a few cycles.
  • Scope narrowly at first (by platform or scenario subset), then expand.

Troubleshooting​

  • “No policies found”: create your first one or use a Template (see Templates guide).
  • “Validation didn’t change”: confirm the policy is enabled and scope includes the scenario.
  • Validate & Fix
  • Templates
  • Governance
  • Alerts