Skip to main content
Workspaces are collections of Deployments that can be accessed by a specific group of users. You can use Workspaces to group Deployments that share a business use case or trait. Some common ways to implement Workspaces are:
  • Using a single Workspace for an entire Organization, with all development and production pipelines hosted together.
  • Using a Workspace per team. For example, you might have a Workspace for your Data Science team and a separate Workspace for your Data Engineer team, with each team’s Workspace hosting both production and development pipelines.
  • Using a Workspace per project. For example, you might have a Workspace called “Sales Analytics Project” that hosts both production and development pipelines.
This document explains how to configure Workspace details. To manage Workspace users, see Manage Workspace users.
A new Astro UI is hereAstronomer has redesigned the Astro UI. Try the new experience and switch your instructions using the New Astro UI and Legacy UI tabs on this page. Your selection is remembered across the docs.

​
Create a Workspace

To create a Workspace, you must have an Organization-level role.
  1. In the Astro UI, go to Settings > Workspaces.
  2. Click + New Workspace.
During this initial setup, you can configure the Workspace’s name and description. You can update all other Workspace settings later from the Workspace’s settings.
The new Astro UI doesn’t have a separate Workspace view. To scope to a specific Workspace, use the Workspace dropdown in the Deployments, Dags, and Environment sections. To manage a Workspace’s settings, go to Settings > Workspaces, then select the Workspace.

​
Update general Workspace settings

  1. In the Astro UI, go to Settings > Workspaces, then select your Workspace.
  2. In the General section, click Edit, update the Name and Description as needed, then click Save.
  3. To set the CI/CD enforcement default, toggle CI/CD Enforcement in the Deployment Defaults section. This determines whether new Deployments in the Workspace enforce CI/CD deploys by default, and can be overridden at the Deployment level. See Enforce CI/CD deploys.
The Deployment Defaults section also sets the default destination for new Deployments in the Workspace. See Set a default Deployment destination.

​
Set a default Deployment destination

A Workspace’s default Deployment destination is the cluster that new Deployments use when you don’t choose one yourself. It applies whether you create the Deployment in the Astro UI, with the Astro CLI, or with the Astro API. It also applies to ephemeral test Deployments in the Astro IDE. You can set one of two destination types:
  • Standard Cluster: A cloud provider and region. Astro creates new Deployments on a standard cluster in that region.
  • Dedicated Cluster: A specific dedicated cluster. Astro creates new Deployments on that cluster.
The two types are mutually exclusive. Selecting a dedicated cluster clears the cloud provider and region, and the other way around. For a comparison of the two cluster types, see Cluster type.
  1. In the Astro UI, go to Settings > Workspaces, then select your Workspace.
  2. In the Deployment Defaults section, click Edit next to Cluster.
  3. For Type, select Standard Cluster and choose a Cloud Provider and Region, or select Dedicated Cluster and choose a cluster.
  4. Click Save.
The Deployment Defaults section shows the current default next to Cluster:
  • A standard destination appears as Standard with its cloud provider and region, such as Standard - GCP - europe-west1.
  • A dedicated destination appears as the cluster’s name with its cloud provider and region.
  • No default appears as Not set.
A default destination doesn’t restrict where Deployments run. Anyone who creates a Deployment can choose a different cluster type, cloud provider, region, or cluster. To require that all new Deployments use a dedicated cluster, see Enforce dedicated clusters for new Deployments.

​
How Astro resolves a Deployment’s destination

When you create a Deployment, Astro resolves the destination in the following order and stops at the first match:
  1. The cluster, cloud provider, and region you choose when you create the Deployment.
  2. The Workspace’s default destination.
  3. The only cluster in the Organization, if the Organization has exactly one.
  4. A standard Microsoft Azure cluster in the default region. This last fallback doesn’t apply if your Organization enforces dedicated clusters.
Because Astro checks your own selection first, passing --cluster-id or --cloud-provider to astro deployment create, or setting clusterId or cloudProvider in an API request, overrides the Workspace default. If your Organization has more than one cluster and neither you nor the Workspace specifies a destination, Astro returns an error instead of choosing a cluster for you. You can also set the default destination with the defaultClusterId, defaultCloudProvider, and defaultRegion fields in the Astro API. See Update Workspace.

​
Configure Otto investigation guidance

Otto investigation guidance is custom text you provide to tailor Otto investigations to your environment. For example, you can instruct Otto to treat tasks that begin with validate as non-blocking data quality tests, or to interpret a specific log pattern in a particular way. Guidance set at the Workspace level applies to every Deployment in the Workspace. Individual Deployments can override it. See Configure Otto investigation guidance for a Deployment.
  1. In the Astro UI, go to Settings > Workspaces, then select your Workspace.
  2. In the AI Agents section, click the Edit icon next to Otto Investigation Guidance.
  3. Enter up to 10,000 characters of markdown guidance, then save your changes.

​
Delete a Workspace

  1. In the Astro UI, go to Settings > Workspaces, then select your Workspace.
  2. Scroll to the Danger Zone section, then click Delete Workspace. This option isn’t available when there are active Deployments in the Workspace.
  3. In the confirmation dialog, enter delete and then click Yes, Continue.