Automation Cloud admin guide

Last updated Mar 28, 2025

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 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 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.

Important: 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.

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

Users invited to an organization can view 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 view data and interact with the different services until they are granted the required roles.

Orchestrator in your organization

All Automation Cloud^TM tenants contain an Orchestrator service.

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

An Automation Cloud^TM tenant is different from an Orchestrator tenant.

The following table describes the differences between an Automation Cloud^TM tenant and an on-premises Orchestrator tenant.

Tenant in Automation Cloud^TM	Tenant in on-premises Orchestrator
Is a subdivision of the Automation Cloud^TM organization	Is a subdivision of the Orchestrator instance
Includes one Orchestrator service	Is a part of Orchestrator
Includes several other cloud services (UiPath® products), all within Automation Cloud^TM	Is not in the same medium as your other UiPath products and interacts with them through integrations

Note: For more information about the differences between on-premises Orchestrator and the Orchestrator service in Automation Cloud^TM, also refer to Orchestrator differences .

Viewing tenants

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

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

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:

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, select the tenant list in the top right and select another tenant: