Subscribe

UiPath Automation Cloud™

UiPath Automation Cloud™ Guide

For information about the current status of Automation Cloud and our cloud services, see the Status page.

Managing tenants

👍

For examples on how you can use tenants to create separation of resources within your organization, see Examples of platform modelling.

 

Adding tenants


::label-Enterprise-label:: Community organizations are limited to one tenant, which is created automatically. You can create more tenants if you are on the enterprise or enterprise trial licensing plan.

To create a new tenant:

  1. Go to Admin.
  2. In the left panel, click + next to the Tenants header to add a tenant:
491491

The Create a new tenant wizard opens on the first step, General.

  1. Enter a name for your tenant in the Tenant Name field.
    You can enter up to 32 alphabetical or numeric characters, starting with a letter. No spaces or special characters are allowed.
    You can change the tenant name later, but there are consequences.
  2. (Optional) From the Color list to the right of the Tenant Name field, choose a color to show in the header when this tenant is selected.
    This can help users easily tell which tenant they're currently working in:
12701270
  1. If you want to use this tenant as a canary tenant, select Use as a canary environment.
    For more information, see Using a canary tenant.
    If you already have a canary tenant, even if it is currently disabled, you cannot select the checkbox to create another canary tenant.
  2. From the Tenant Region list, choose the region for hosting your service data for this tenant.
    You cannot change the tenant region after you create the tenant. If you need to change it later, you must open a Support ticket.
  3. Click Next to proceed to the next step.
  4. Select the checkboxes for the services that you want to make available within the new tenant.
    The Orchestrator service is mandatory. Other services are only available if you have free licenses for the service.
12081208

If a service is only available in a different region than the selected tenant region, the region where that particular service will be hosted is displayed on the card for the service. Tenant and service regions

  1. Click Next to proceed to the next step.
    On the License Allocation step, we automatically fill in the license quantities to allocate all your free licenses to the tenant.
  2. If you want to keep some of your available licenses for other tenants, reduce the quantity for each license type to the amount you want to allocate to this tenant.
    The number of licenses you have available is displayed under each license type. This is the number of licenses you have before creating this tenant and out of which you can allocate to this tenant.
  3. Click Create to close the wizard and create the tenant.

The new tenant is added to the Tenants panel on the left.
The loading icon is displayed while tenant provisioning is in progress.
After the icon disappears:

  • The tenant and its services are ready for use.
  • The tenant is available to users from the tenant picker in the top right of the page, but they only have read-only access.

Next steps: 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, see:

 

Changing the tenant region

Enterprise customers can choose the region of tenants when creating them. However, after creating the tenant you cannot change the region yourself.
If you need to move a tenant to a different region, open an SLA ticket and request the move to one of the available regions.

 

Using a canary tenant

📘

This feature is only available when the new Admin experience is enabled.
If you are still using the old Admin experience, you must turn on the new Admin experience to use a canary tenant.

You can add a canary tenant to your organization to view and test upcoming changes before they reach your other tenants. The canary tenant serves as an isolated medium that uses your current setup where you can check on the impact that upcoming changes have within the context of your current organization.

🚧

Important

Do not use the canary tenant for production.


This feature is a medium made available to you for testing purposes only and does not benefit from the same enterprise commitments as your other tenants.


The uptime guarantee offered by your enterprise plan does not apply to the canary tenant.


While we encourage reporting any potential issues you encounter within the canary tenant, please note that we will address them on a best-effort basis only.

Early access window

The canary tenant receives updates to enterprise functionality for all of the supported services as soon as they are announced in the release notes, while your other tenants receive them at least 3 days later.
For more information about delayed feature availability, see When do changes become available.

Benefits

With a canary tenant, you can:

  • view and test enterprise-only features before they reach enterprise environments
  • test and run the same automations that you use in production.

Included services

Only the following UiPath cloud services are available to be provisioned in a canary tenant:

Service name

Notes

Release notes

Orchestrator

Data retention for Orchestrator within the canary tenant is reduced to the thresholds for community plans.

Orchestrator release notes

If a service is not listed in the above table, then it does not receive early updates in the canary tenant.

📘

Licensing required

To provision a service in your canary tenant, you need to have licenses for that service.

Data residency

The canary tenant and its service data is always hosted in the European Union (Europe) region and you cannot choose a different region.

Tips

To make the most of your canary tenant, we recommend setting it up in the same way as your production tenants. This includes replicating the same:

  • tenant settings in UiPath Orchestrator
  • service-level settings for each of the services you provisioned in the canary tenant
  • service-level roles and user licenses for your users
  • automations in Orchestrator - You can use the UiPath Orchestrator Manager to copy data from one of your tenants to the canary tenant.

 

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. Click Settings.
    The Settings page for the selected tenant opens.
  3. Edit the tenant name if needed.
    Changing a tenant's name disconnects your Robots and Mobile Orchestrator users, and invalidates any pending user invites. See 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. Click 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 Automation Cloud service configurations:

  • Robots configured at Orchestrator services level are disconnected. Reconnect your Robots, 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.
  • User invites sent before the change are not valid anymore. Send new invites for your colleagues who haven’t joined yet.

 

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. Click Settings.
    The Settings page for the selected tenant opens.
  3. Under Disable Tenant, click Enable or Disable, depending on the current state of the tenant.
    A warning dialog opens.
  4. In the dialog, click 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.

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. Click Settings.
    The Settings page for the selected tenant opens.
  3. Under Delete tenant permanently, click 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 click 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 > Tenant > Licenses, you can see information about the licenses currently allocated to each tenant.

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

For more information, see Allocating licenses to tenants.

Updated 19 days ago


Managing tenants


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.