- First Time Configuration
- Host Administration
- Organization Administration
- Accounts and Roles
- Licensing
- Notifications
About Automation Suite
Automation Suite enables you to deploy the UiPath® business automation platform in your environment of your choice. Depending on your needs, you can deploy the platform on Linux servers (bare-metal or virtual machines) in your data center or public cloud (Azure, AWS, or GCP), or on your Kubernetes clusters in Amazon Web Services (Elastic Kubernetes Service) or Microsoft Azure (Azure Kubernetes Service).
Automation Suite includes:
-
All server products (except for any new products shipping in Automation Cloud first).
-
All shared suite capabilities that enable you to easily configure the integration with existing enterprise systems, such as AD, AAD, or SAML, across all products; a common experience is offered across the suite for the user, tenant, external applications, and license management.
-
Common end-user portal.
This guide provides documentation for all users on how to use the portal. For administrators, it explains how to set up the organization security, authentication, and other settings.
The UiPath platform operates on a hierarchy system with different levels, allowing for organized and efficient setting management across multiple companies and departments.
|
Term |
Details |
|---|---|
|
Host |
The host level is the top tier in UiPath platform hierarchy. This is where system administrators perform configurations for underlying organizations and create new organizations. Settings configured at the host level are applicable to all its organizations. However, these settings can either be overwritten at each organization level according to its needs or remain unchanged. |
|
Organization |
An organization typically represents a single company within the host. It can have its own specific settings or inherit the ones from the host level. An organization admin manages these settings. If needed, they can change the settings received from the host level, tweaking the configurations to match their organization's requirements. |
|
Tenant |
A tenant represents a distinct entity such as a separate division or department within the organization. Each tenant is allotted its own unique resources within the organization, permitting them to handle their automation procedures independently. A tenant's function can be managed by service assignments made for it. |
|
Service |
Services represent various UiPath web products or modules, such as Orchestrator, Insights, or Action Center. Each service does a unique job in the automation process. The services can be allotted to any tenant for their individual automation needs. |
|
Folder |
Folders are a level under a tenant and serve as a platform for even more detailed segregation of resources within a tenant. These resources might include different processes, assets, or credentials. |
|
User, Robot Accounts, Groups, and External Apps | These entities are identified by UiPath in order to assign access rights and permissions. User Accounts: Are the individual users of UiPath, each having unique access based on assigned roles and licenses. Robot Accounts: Are used to run automated processes and have special permissions based on robot's role and automation requirements. Groups: Are collections of users who share the same access, permissions, roles, and licenses in UiPath. External Apps: These are third-party applications that interact with UiPath, each with its own permissions, roles and licenses. |
The UiPath platform operates on a hierarchy system with different levels, allowing for organized and efficient setting management across multiple companies and departments.
|
Term |
Details |
|---|---|
|
Host |
The host level is the top tier in UiPath platform hierarchy. This is where system administrators perform configurations for underlying organizations and create new organizations. Settings configured at the host level are applicable to all its organizations. However, these settings can either be overwritten at each organization level according to its needs or remain unchanged. |
|
Organization |
An organization typically represents a single company. An organization admin manages organization settings. It can have its own specific settings or inherit the ones from the host level. |
|
Tenant |
A tenant represents a distinct entity such as a separate division or department within an organization. Each tenant is allotted its own unique resources within the organization, permitting them to handle their automation procedures independently. |
|
Folder |
Folders are a division under a tenant, and are used as containers for automation, tasks, robots, packages, queues, assets, and others in a more manageable way. Folders provide an efficient way to manage access rights and help set fine-grained permissions. |
|
User accounts, Robot accounts, Groups, and External apps | Identifies used to assign access rights and permissions.
|
System administrators define settings at the host level that apply to all underlying organizations. However, in case a specific organization has unique needs, an organization administrator has the flexibility to modify or overwrite these inherited settings. This enables both uniformity and customization within the platform.
The below diagram depicts the hierarchical relationship between the host, organization, tenant, and service.
