Subscribe

UiPath Automation Suite

The UiPath Automation Suite Guide

About the Automation Suite experience

Automation Suite is UiPath's self-hosted solution for managing all of your UiPath products as one.

Now that you've successfully installed Automation Suite, with all of the products it includes, let's get you started with the basics.

Main platform concepts


Automation Suite is not a product per se, it is our on-premises automation platform. What this means is that, to manage all your UiPath products as one platform, you can find options and configurations at several levels: platform, organization, tenant, or product.

Here are a few platform concepts to understand before you dive into the Configuration checklist.

Term

Details

Service

The UiPath products you have installed are available in Automation Suite as services in a shared environment, rather than as stand-alone products.

Host

The host level is the highest shared layer in Automation Suite.
A system administrator is appointed at installation who has access to the host portal, from where they can configure host settings, such as adding additional system administrators, create organizations, license Automation Suite at the host level, and more.
The system administrator can also access the Orchestrator host portal to define settings that should apply to all Orchestrator instances across all organizations and tenants.

Organization

The organization is the second-highest logical layer in Automation Suite and it is the highest layer visible to your users. It typically corresponds to one company.
An organization can be licensed from the host level or have a stand-alone license. Accounts, organization settings, and services are shared throughout the organization and inherited by tenants.
An organization administrator is appointed when the system administrator creates the organization, and this user can configure all aspects of the organization.

Tenant

A tenant is a logical container within an organization that allows you to separate your business flows and information, like in real-life organizations. By using more than one tenant, you can split a single instance of Orchestrator into multiple deployment environments, each with its own robots, processes, logs, and so on. This lets you isolate the desired resources from the rest of the organization and have automation resources accessible only from within that tenant.

Accounts

These are identities that represent either an employee (user account), or a robot entity (robot account). They are used so that you can assign roles and licenses to a particular identity. For your employees to be able to access Automation Suite, you must create user accounts for them in Automation Suite.

 

Hierarchies and inheritance


The below diagram depicts the hierarchical relationship between the host, organization, tenant, and service.
Settings from a superior level are always inherited at the inferior levels, but some can be overwritten.

For example, the email address used for system notifications is defined at the host level, from Global Settings. This email address is used to send out system notifications for all organizations, all tenants, and all Orchestrator service instances.

Updated 9 days ago


About the Automation Suite experience


Suggested Edits are limited on API Reference Pages

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