- Getting started
- About Automation Suite
- Getting started with the platform
- Exploring the user interface
- Managing user preferences
- Understanding authentication models
- Software requirements
- Host administration
- Organizations
- Tenants and services
- Authentication and security
- Licensing
- Accounts and roles
- External applications
- Notifications
- Logging
- Troubleshooting
Automation Suite Admin Guide
Getting started with the platform
The UiPath platform operates on a hierarchy system with different levels, allowing for organized and efficient setting management across multiple companies and departments.
Layer |
Description |
---|---|
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. An organization can have its own specific settings or inherit the ones from the host level. |
Tenant |
A tenant is a unique and separate division or department within an organization. Each tenant has its own resources, separated from other tenants within the organization. |
Folder |
Folders are a division under a tenant, and are used as containers for different resources, such as automations, robots, assets, and others. Folders provide an efficient way to manage access rights and help set fine-grained permissions. |
User accounts, Robot accounts, Groups, and External apps | Identities used to assign access rights and permissions.
|
System administrators define settings at the host level that apply to all underlying organizations. However, in case an organization has unique needs, the organization administrator has the flexibility to modify or overwrite these inherited settings. This enables both uniformity and customization within the platform.
The following diagram depicts the hierarchical relationship between the host, organization, tenant, and service:
There are two primary user persona categories, administrators and non-administrators, and they encompass distinct roles and responsibilities within the platform. This page is dedicated to illustrating the typical journey taken by both personas when they first start using the platform.
The platform automatically categorizes users into different implicit user personas based on the type of license they possess. These implicit user personas are used to tailor the user experience to their specific needs and responsibilities.
-
Admin users - are not mapped based on their licenses but based on their membership in the Administrators user group.
-
Non admin users - Non-admin users are mapped based on their licenses.
User persona |
License |
---|---|
Administrator - configures organization settings, user access controls, and oversees the efficient operation of the platform |
Not mapped based on license, but on their membership in the Administrators user group. |
RPA developer - designs automations in Studio that meet the organization automating requirements. |
Automation Developer - Named User and Multiuser |
Citizen developer - runs automations designed by RPA developers, completes actions, creates quick automations using StudioX. | Citizen Developer - Named User and Multiuser |
Business user - runs automations designed by RPA developers, completes actions |
Attended - Named User and Multiuser Action Center - Named User and Multiuser |
Analyst - identifies processes that can be simplified, digitized, or eliminated, uses metrics to create reports |
Insights Designer User |
Tester - tests RPAs and other software within Studio, creates test environments. | Tester - Named User |
UiPath administration consists of two hierarchical levels, namely, host and organization. Each of these levels is configured via dedicated administration portals.
-
Host portal: The host is the first level in the hierarchy. At this level, you can modify shared platform functionality like system administrator accounts, global authentication settings, global system email settings. Only system administrators can access the host portal. Host settings apply across all the organizations.
-
Orchestrator host portal: The Orchestrator portal gives access to Orchestrator host settings. Only system administrators can access the Orchestrator host portal. Host settings apply across all the organizations.
-
Organization admin portal: The Admin area at the organization level is where you can view and manage organization administrator accounts, organization authentication settings, organization system email settings, and other security settings. Only organization administrators (logged in to the organization) can access the organization Admin area.
The Management portal at the host level is where you can view and manage system administrator accounts,global authentication settings, global system email settings, the login page. Only system administrators (logged in to the host) can access host portal.
The settings that you configure from this portal are inherited by all your organizations. Some settings can be overwritten at the organization level.
https://
AutomationSuiteURL
/
, and log in to the host
with your system administrator credentials.
The Orchestrator host portal is available from within the host portal. It allows system administrators to configure Orchestrator settings at the host level.
https://
AutomationSuiteURL
/
and log in to the host
with your system administrator credentials.
The Admin area at the organization level is where you can view and manage organization administrator accounts,organization authentication settings, organization system email settings and other security settings. Only organization administrators (logged in to the organization) can access the organization Admin area.
https://
AutomationSuiteURL
/
and log in to the organization
with your organization administrator credentials. Once logged in, navigate to Admin from the left rail.