Manage Teams as Code

Teams are Dash0 assets that can be versioned and managed as infrastructure as code. This approach enables version control, automated deployment pipelines, consistent access-management policies across environments, and code review for team membership changes.

Teams are organization-scoped resources. Unlike dashboards, views, or check rules, a team is not tied to a dataset — the same team applies across every dataset in the organization.

Team membership is expressed as a list of email addresses. The Dash0 backend resolves each email to an internal user id during reconciliation. If an email does not match a member of the organization, the write fails with a single 400Copy listing every offender, so a typo cannot silently create a partial team.

Dash0 Operator for Kubernetes

Define teams as Dash0TeamCopy custom resources that sync to Dash0, enabling GitOps workflows and native Kubernetes management.

Example

123456789101112131415
apiVersion: dash0.com/v1alpha1
kind: Dash0Team
metadata:
  name: backend
  namespace: dash0-system
spec:
  display:
    name: Backend
    description: Owns backend services and the data platform.
    color:
      from: "#6366F1"
      to: "#8B5CF6"
  members:
    - alice@example.com
    - bob@example.com

The Dash0 Operator for Kubernetes watches for Dash0TeamCopy resources in namespaces where a Dash0MonitoringCopy resource is deployed. When it detects changes:

• New team resources are created as teams in Dash0.
• Modified resources update the corresponding teams.
• Deleted resources remove the corresponding teams.

The operator derives a deterministic origin from the custom resource's metadata, so cluster rebuilds re-adopt existing teams without duplication.

Apply and Manage

1234567891011121314
# Apply the team
kubectl apply -f team.yaml

# List all teams
kubectl get dash0teams -n dash0-system

# View details and synchronization status
kubectl describe dash0team backend -n dash0-system

# Update the team
kubectl edit dash0team backend -n dash0-system

# Delete the team
kubectl delete dash0team backend -n dash0-system

For more information, refer to the Dash0 Operator for Kubernetes documentation.

Dash0 Terraform Provider

Manage teams in your Terraform infrastructure alongside other cloud resources for unified infrastructure management.

Example Usage

1234567891011121314151617181920212223242526272829303132
terraform {
  required_providers {
    dash0 = {
      source  = "dash0hq/dash0"
      version = "~> 1.0"
    }
  }
}

provider "dash0" {
  url        = "https://api.dash0.com"
  auth_token = "auth_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}

resource "dash0_team" "backend" {
  team_yaml = <<-EOT
    apiVersion: dash0.com/v1alpha1
    kind: Dash0Team
    metadata:
      name: backend
    spec:
      display:
        name: Backend
        description: Owns backend services and the data platform.
        color:
          from: "#6366F1"
          to: "#8B5CF6"
      members:
        - alice@example.com
        - bob@example.com
  EOT
}

The provider stamps a stable origin onto the team on create, so state loss does not orphan the resource — a subsequent terraform applyCopy recovers the existing team by origin instead of creating a duplicate. The idCopy attribute is computed and available for downstream references.

For more information, see the dash0_teamCopy resource documentation.

Dash0 CLI

Script team operations with the Dash0 CLI for automated deployments and batch operations. Because teams are organization-scoped, no --datasetCopy flag is required.

Apply from File

12
# Create or replace a team from a YAML file (works on the standard apply pipeline)
dash0 apply -f team.yaml

List Teams

12
# List all teams in the organization
dash0 -X teams list

Get Team Details

12345
# Get a single team as YAML — round-trippable with `dash0 apply -f`
dash0 -X teams get <origin-or-id> -o yaml

# Get team details in JSON format
dash0 -X teams get <origin-or-id> -o json

The exported YAML round-trips through apply -fCopy without post-processing. Membership always renders as email addresses on read, regardless of how the write specified them.

Update Team

12
# Update an existing team by re-applying the edited YAML
dash0 apply -f team.yaml

Delete Team

12
# Delete a team by origin or id
dash0 -X teams delete <origin-or-id> --force

For more information, see the Dash0 CLI command reference.

Further Reading

• About Teams — Understand what teams are and how they organize members and shared resources.
• About Managing as Code — Compare the three infrastructure-as-code tools for teams.
• Manage Views as Code — Manage saved queries as infrastructure as code.
• Manage Dashboards as Code — Define and manage dashboards using infrastructure as code.
• Manage Check Rules as Code — Define and manage check rules using infrastructure as code.