# Managing tenants

> :::tip
For examples on how you can use tenants to create separation of resources within your organization, refer to [Examples of platform modelling](https://docs.uipath.com/overview-guide/docs/platform-guidelines-for-partners#examples-of-platform-modelling).
:::

:::tip
For examples on how you can use tenants to create separation of resources within your organization, refer to [Examples of platform modelling](https://docs.uipath.com/overview-guide/docs/platform-guidelines-for-partners#examples-of-platform-modelling).
:::

## Adding tenants

To create a new tenant, take the following steps:

1. Navigate to **Admin** in the Private Test Cloud portal.
2. In the **Tenants** view, select the **Plus** icon. The **Create new tenant** process starts with three steps to follow.
3. On the **General** step, provide the following information:
   1. Enter a name for your tenant in the **Name** field.

      You can enter up to 32 alphabetical or numeric characters, starting with a letter. No spaces or special characters are allowed.

      :::important
      You can change the tenant name later, but there are consequences. Refer to [Changing the tenant name](https://docs.uipath.com/test-cloud/automation-suite/2.2510/admin-guide/managing-tenants#changing-the-tenant-name-or-color).
      :::
   2. (Optional) Select a color from the **Color** picker to identify your tenant in the header when operating within that tenant.
   3. Select a tenant type from the **Environment type** section.

      Environment type is a categorization label for organizational purposes. It does not currently affect service behavior, feature availability, or update rollout. Select the type that matches your tenant's intended use (Production, Staging, or Development) for easier identification.

      You can choose from three types of environments:

      * **Production** tenants allow the latest versions of software, products, or updates to be pushed to users live.
      * **Development** tenants are used for development purposes without impacting live or operational tenants.
      * **Staging** tenants are used for testing purposes without impacting live or operational tenants

   
4. Select **Next** to proceed to the **Add services** step.
5. On the **Add services** step, select the checkboxes for the services that you want to make available within your new tenant.

   The Orchestrator service is mandatory. Other services are only available if you have free licenses for them.
6. Select **Next** to proceed to the **License allocation** step.

   On the **License allocation** step, you can observe the available number of licenses for each type that you can allocate to your new tenant. If you want to keep some of the available licenses for other tenants, you can allocate a lower number of licenses to your new tenant from each of the available license types.
7. Select **Create** to close the wizard and create the tenant.

   The new tenant is added to the **Tenants** panel and the tenant picker.

   Production type tenants can be identified through the !['Production tenant' image](https://dev-assets.cms.uipath.com/assets/images/test-cloud/test-cloud-production-tenant-image-541698-52507f20-345687be.webp) icon. Non-production type tenants can be identified through the !['Non-production tenant' icon](https://dev-assets.cms.uipath.com/assets/images/test-cloud/test-cloud-non-production-tenant-icon-541706-cf0b8412-a9b60777.webp) icon.

To be able to work in the tenant, you or a service administrator must assign roles and licenses for the services in the new tenant to users. For more information, refer to:

* [About accounts and groups](https://docs.uipath.com/test-cloud/automation-suite/2.2510/admin-guide/about-accounts#about-accounts-and-groups)
* [Assigning user licenses](https://docs.uipath.com/test-cloud/automation-suite/2.2510/admin-guide/allocating-user-licenses#assigning-user-licenses)

## Editing tenants

When editing tenant settings, you can change the name, color, enable, disable, or delete the tenant.

### Changing the tenant name or color

1. Go to **Admin** and select the tenant in the panel on the left.
2. Select **Settings**.

   The **Settings** page for the selected tenant opens.
3. Edit the tenant name if needed.
   :::important
   Changing a tenant's name disconnects your Robots and Mobile Orchestrator users, and invalidates any pending user invites. Refer to **Impact of Changing Tenant Names**.
   :::
4. From the list to the right of the name, select a different header color for the tenant, if needed.
5. Select **Save Changes** at the bottom of the page.

   A confirmation message appears in the top right of the screen.

#### Impact of changing tenant names

Changing the name of any of your tenants greatly impacts your previous UiPath service configurations:

* Robots configured at Orchestrator services level are disconnected. [Reconnect your robots](https://docs.uipath.com/orchestrator/automation-suite/2.2510/user-guide/connecting-robots-to-orchestrator), entering the new URLs.
* Service URLs previously bookmarked don't work anymore. Send your users the new URLs.
* Mobile Orchestrator users are disconnected. Send them the new service URLs to connect again.

### Enabling or disabling a tenant

Disabled tenants remain visible to organization administrators in the **Tenants** panel of the **Admin** page, but the tenant and its services are no longer available to users. Also, the licenses that were allocated to the tenant are released and returned to the organization's pool of licenses.

All data for the services is kept. You can later enable the tenant to access its services again.

1. Go to **Admin** and select the tenant in the panel on the left.
2. Select **Settings**.

   The **Settings** page for the selected tenant opens.
3. Under **Disable Tenant**, select **Enable** or **Disable**, depending on the current state of the tenant.

   A warning dialog opens.
4. In the dialog, select **Enable** or **Disable** to proceed.

   A loading icon is shown next to the tenant in the **Tenants** panel on the left while the change is being processed.

   After the icon disappears:

   * If you disabled the tenant, **Disabled** appears to its right and the tenant and its services are no longer available to users.
   * If you enabled the tenant, it is now restored as it was before being disabled. All licenses that it used before are also re-allocated if they were available in the organization pool. The tenant and its services are now available for use.

### Deleting a tenant

When deleting a tenant, you remove the tenant from your organization and also delete all of its services and any service data.

After deleting a tenant, all its licenses are freed up and available for you to allocate to other tenants.

:::note
If any processes are being executed in the tenant's Orchestrator service, you cannot delete the tenant.
:::

1. Go to **Admin** and select the tenant in the panel on the left.
2. Select **Settings**.

   The **Settings** page for the selected tenant opens.
3. Under **Delete permanently**, select **Delete**, depending on the current state of the tenant.

   The **Delete Tenant** dialog opens.
4. In the field, enter the tenant name, exactly as it is shown, including the letter case, and then select **Delete**.

   A loading icon is displayed next to the tenant in the Tenants panel while the deletion is in progress. When complete, the tenant is removed from the Tenants panel.

## Editing tenant licenses

In **Admin &gt; Tenant &gt; Licenses**, you can view information about the licenses currently allocated to each tenant.

To change the license quantities, select **Edit allocation** in the top right corner.

For more information, refer to [Allocating licenses to tenants](https://docs.uipath.com/test-cloud/automation-suite/2.2510/admin-guide/allocating-licenses-to-tenants#assigning-licenses-to-tenants).
