> ## Documentation Index
> Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update settings for your Astro Organization

An Organization is the highest management level on Astro. In addition to configuring infrastructure for your Organization, you can update Organization settings that apply to all clusters, Workspaces, Deployments, and users within the Workspace.

This document includes instructions to configure high-level Organization settings from the Astro UI. To configure more specific Organization-level infrastructure, see:

* [Manage users in an Astro Organization](/docs/astro/manage-organization-users)
* [Set up authentication and single sign-on for Astro](/docs/astro/configure-idp)
* [Create a dedicated Astro cluster](/docs/astro/create-dedicated-cluster)
* [Create and manage Organization API tokens](/docs/astro/organization-api-tokens)

## Prerequisites

* Organization Owner permissions

<Tip>
  **A new Astro UI is here**

  Astronomer 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.
</Tip>

## Update your Organization name

Your Organization name is a human-readable name that appears in the Astro UI and in the Astro CLI. Updating your Organization name is a cosmetic change that has no affect on any unique Organization information, such as your Organization ID, which persists for the lifetime of the Organization.

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    1. In the Astro UI, go to **Settings**.
    2. In the **Organization Name** row, click the **Edit** pencil.
    3. Enter the new Organization name.
    4. Click **Save**.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    1. In the Astro UI, click **Organization Settings**. This opens the **General** Organization page.
    2. In the **Organization Detail** section, click **Edit Details**.
    3. Give your Organization a new **Organization Name**, then click **Update Organization**.
  </Tab>
</Tabs>

## Configure environment secrets fetching for the Astro Environment Manager

When members of your Organization create a local Airflow environment using the Astro CLI, they can pull connections configured in the [Astro Environment Manager](/docs/astro/create-and-link-connections) based on their Workspace credentials. This enables users to share connection details between Astro and their local Airflow environments and avoid creating connections twice. See [Import and export Airflow connections and variables](/docs/cli/v1.43/local-connections) for more details.

You can enable or disable this feature based on whether you want Organization members to access Astro-configured connection details from their local machines.

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    1. In the Astro UI, go to **Settings**.
    2. Scroll to the **Organization Policies** section.
    3. Click the **Environment Secrets Showable** toggle to enable or disable the feature.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    1. In the Astro UI, click **Organization Settings**. This opens the **General** Organization page.
    2. In the **Organization Detail** section, click **Edit Details**.
    3. Click the **Environment Secrets Fetching** toggle to **Enabled** or **Disabled**, then click **Update Organization**.
  </Tab>
</Tabs>

## Enforce dedicated clusters for new Deployments

Organization Owners can restrict new Deployments to dedicated clusters only. When you enable **Enforce Dedicated Clusters**, Astro rejects requests to create new Deployments on standard clusters, both in the Astro UI and through the Astro API. Existing Deployments on standard clusters continue to run without changes.

This setting is available to eligible Organizations.

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    1. In the Astro UI, go to **Settings**.
    2. Scroll to the **Organization Policies** section.
    3. Click the **Enforce Dedicated Clusters** toggle to enable or disable it.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    <Steps>
      <Step title="1. Open Organization settings">
        In the Astro UI, click **Organization Settings**. This opens the **General** Organization page.
      </Step>

      <Step title="2. Edit Organization details">
        In the **Organization Detail** section, click **Edit Details**.
      </Step>

      <Step title="3. Toggle enforce dedicated clusters">
        Find the **Enforce Dedicated Clusters** option. Set the toggle to **Enabled** to require new Deployments to use a dedicated cluster, or **Disabled** to allow new Deployments on standard clusters.
      </Step>

      <Step title="4. Save changes">
        Click **Update Organization** to apply your changes.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Configure security contacts

*Security contacts* are email addresses, other than Organization Owners, that receive security notifications for your Organization.

<Tabs>
  <Tab title="New Astro UI" language="astro-next-ui">
    1. In the Astro UI, go to **Settings**, then scroll to the **Security** section.
    2. Next to **Security Contacts**, click the **Edit** pencil.
    3. To add an address, click **+ Add Email** and enter a valid email. To remove an address, click the trash can next to it.
    4. Click **Update Security Contacts**.
  </Tab>

  <Tab title="Legacy UI" language="legacy-ui">
    <Steps>
      <Step title="1. Open Organization settings">
        In the Astro UI, click **Organization Settings**. This opens the **General** Organization page.
      </Step>

      <Step title="2. Edit security contacts">
        In the **Security Contacts** section, click **Edit**.
      </Step>

      <Step title="3. Add or remove email addresses">
        Click **Add Email** to add an entry, or click **Remove** next to an existing entry. Each address must be a valid email.
      </Step>

      <Step title="4. Save changes">
        Click **Update Security Contacts**.
      </Step>
    </Steps>
  </Tab>
</Tabs>
