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.

About tenants

Tenants allow you to model your organization structure, separating your business flows and information just like in real-life organizations. They are containers where you can organize your services and manage them for a group of users. For example, you can create tenants for each of your departments and decide what services you want to enable for each, based on their needs. In each tenant, you can have one instance of each of the cloud services.

 

Default tenant


When you get started with an Automation Cloud organization, your first tenant, called DefaultTenant, is automatically created.

 

Multitenancy


If your organization is on the Enterprise or Enterprise Trial licensing plans, you can create multiple tenants for your organization's needs. Multitenancy enables you to isolate data within your Automation Cloud organization. This feature facilitates automating different departments from your company and lets you control access to data per department.
Organizations on the Community licensing plan are limited to one tenant.

🚧

For organizations that already have multiple Orchestrator services prior to launching the Tenants feature, a tenant is automatically created for each existing Orchestrator service, incorporating that service, with the tenant name inherited from the Orchestrator service.

All the data is stored in the cloud, in a database shared between only your tenants.

Users invited to an Automation Cloud organization can see all tenants within the organization by default and all the services they contain, with a few exceptions. This allows users to request access and engage in using them based on their business needs.
However, users cannot see data and interact with the different services until they are granted the required roles.

 

Orchestrator in Automation Cloud


All Automation Cloud tenants contain an Orchestrator service.

While in on-premises Orchestrator, your Orchestrator instance can include several tenants, in Automation Cloud you have one Orchestrator service in each Automation Cloud tenant.

An Automation Cloud tenant is different from an Orchestrator tenant.

Tenant in Automation CloudTenant in On-premises Orchestrator
Is a subdivision of the Automation Cloud organizationIs a subdivision of the Orchestrator instance
Includes one Orchestrator serviceIs a part of Orchestrator
Includes several other cloud services (UiPath products), all within Automation CloudIs not in the same medium as your other UiPath products and interacts with them through integrations

For more information about the differences between on-premises Orchestrator and the Orchestrator service in Automation Cloud, also see Orchestrator differences.

 

Viewing tenants


Organization administrators can see and manage all of the tenants in their organization.

All existing tenants are displayed on the Admin page, in the panel on the left:

12081208

 

Tenant statuses

Tenants can be in one of two states:

  • Enabled - the tenant is active and can be accessed by users.
  • Disabled - the tenant is not active and unavailable to users. Disabled is shown next to the tenant name in the tenants panel:
243243

 

Switching tenants

If your organization has multiple tenants and you have access to more than one, you can switch between tenants while on the page of a tenant-specific service. This lets you work with the data that exists within the selected tenant for the various services, which can be different than what is available in other tenants, or your service-level roles can be different between tenants.

To switch the context in which you are working to a different tenant, click the tenant list in the top right and select another tenant:

13231323

The page refreshes and then shows data for the newly selected tenant.

Updated 3 months ago


About tenants


Suggested Edits are limited on API Reference Pages

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