Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 5, 2026

Configure General Settings

Set up basic automation information including name, description, and category.

General settings provide the basic information that identifies and organizes your automation. These fields help you and your team understand the automation's purpose at a glance.

General automation settings showing name, description, and category fields

Name

The automation name appears in the automations list, run history, and audit logs. Choose a name that clearly describes what the automation does.

  • Best practices: Use descriptive names like "Failed Check Triage" or "Daily SLO Report" rather than generic names like "Automation 1".
  • Uniqueness: Names are not required to be unique. However, using unique names helps distinguish automations in lists and logs.

Description

An optional description provides additional context about the automation's purpose, behavior, or configuration. This field supports plain text and appears in the automation detail view.

  • Best practices: Describe what triggers the automation, what it does, and any important configuration details.
  • Visibility: Visible to anyone with read access to the automation.

Category

The category field organizes automations into logical groups. Use categories to group related automations together.

Common categories:

  • Incident Response: Automations that investigate or respond to failures.
  • Monitoring: Scheduled checks and reports.
  • Deployment: Automations triggered by deployments or releases.
  • PR Review: GitHub pull request analysis and feedback.
  • SLO Tracking: Service level objective monitoring and alerting.

Categories appear in the automations list, making it easier to find and organize related automations.

Permissions

Permissions control who can read, write, or delete the automation. By default:

  • Admins can read and delete all automations.
  • Members can read all automations.
  • The creator automatically gets write and delete permissions.

To grant additional permissions:

  1. Scroll to the Permissions section in the automation editor.
  2. Click Add Permission.
  3. Select a role, user, or team.
  4. Choose actions like agentic_workflow:read, agentic_workflow:write, or agentic_workflow:delete.
  5. Click Save.

Permissions are checked on every API call. Unauthorized attempts are rejected with a 403 Forbidden response.

Enabled State

The Enabled toggle controls whether the automation responds to trigger events. When disabled, the automation remains configured but won't execute.

  • Disabled automations: Still appear in the automations list and can be edited, but won't run when triggered.
  • Default state: New automations are enabled by default. Consider disabling during initial testing, then re-enable for production use.
  • Use case: Disable automations temporarily during maintenance or when troubleshooting.

Further Reading