<commit_before>---
description: Use multiple Auth0 tenants to manage various environments.
topics:
    - dev-tools
    - local-env
contentType: how-to
useCase: development
---
# Set Up Multiple Environments

__Development__, __Test__, __Q&A__ environments are easy to setup in Auth0. Simply create a new tenant for each to guarantee the maximum isolation between these environments. You can easily switch between tenants using the tenant chooser from the top right menu on the dashboard. You can also configure different administrators for each.

::: warning
Moving your tenant to a Development environment will impact [rate limits](https://auth0.com/docs/policies/rate-limits) for calls to the Authentication and Management API.
:::

![](/media/articles/lifecycle/environments.png)

The example above uses a simple naming convention to distinguish each environment, you can name your multiple environments anyway you prefer. No need to use this naming convention, though it is the one recommended.

::: note
If you have a subscription plan costing at least **$167 (USD) per month**, you can request a [child account](/dev-lifecycle/child-tenants) that is identical to your Production account for use in a development/staging/testing environment. This includes paid/upgraded features, as well as individual configuration options, such as Rules. Free accounts do *not* include a child account.
:::

## Set the Environment

For each new tenant created, you should specify its environment. You can assign environment tags to your tenants to differentiate between development, staging, and production environments.

To assign an environment tag to a tenant, go to the [Auth0 Support Center > Tenants](${env.DOMAIN_URL_SUPPORT}/tenants/public). Locate your tenant and click the gear icon to bring up the **Settings** section.

![Support Center Tenants](/media/articles/clients/support-tenants.png)

Next, select the **Assign Environment Tag** option. Use the form to identify your tenant's environment as either `Development`, `Staging`, or `Production`.

If your tenant is mixed use, choose the higher environment. For example, a tenant used for both development and production should be set to `Production`.
<commit_msg>added clarification for child tenant (#6370)<commit_after>---
description: Use multiple Auth0 tenants to manage various environments.
topics:
    - dev-tools
    - local-env
contentType: how-to
useCase: development
---
# Set Up Multiple Environments

__Development__, __Test__, __Q&A__ environments are easy to setup in Auth0. Simply create a new tenant for each to guarantee the maximum isolation between these environments. You can easily switch between tenants using the tenant chooser from the top right menu on the dashboard. You can also configure different administrators for each.

::: warning
Moving your tenant to a Development environment will impact [rate limits](https://auth0.com/docs/policies/rate-limits) for calls to the Authentication and Management API.
:::

![](/media/articles/lifecycle/environments.png)

The example above uses a simple naming convention to distinguish each environment, you can name your multiple environments anyway you prefer. No need to use this naming convention, though it is the one recommended.

::: note
If you have a subscription plan costing at least **$167 (USD) per month**, you can request a [child account](/dev-lifecycle/child-tenants) that is identical to your Production account in terms of paid/upgraded features for use in a development/staging/testing environment. Free accounts do *not* include a child account.
:::

## Set the Environment

For each new tenant created, you should specify its environment. You can assign environment tags to your tenants to differentiate between development, staging, and production environments.

To assign an environment tag to a tenant, go to the [Auth0 Support Center > Tenants](${env.DOMAIN_URL_SUPPORT}/tenants/public). Locate your tenant and click the gear icon to bring up the **Settings** section.

![Support Center Tenants](/media/articles/clients/support-tenants.png)

Next, select the **Assign Environment Tag** option. Use the form to identify your tenant's environment as either `Development`, `Staging`, or `Production`.

If your tenant is mixed use, choose the higher environment. For example, a tenant used for both development and production should be set to `Production`.

{'fraction_non_alphanumeric': 0.06815084052703317, 'fraction_numerical': 0.00408905043162199, 'mean_word_length': 4.894243641231593, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4427318', 'n_tokens_mistral': 1082, 'n_tokens_neox': 1020, 'n_words': 573}