Getting started with the platform

Hierarchies and inheritance

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
Organization	An organization typically represents a single company. An organization admin manages organization settings.
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.
Service	Services represent various UiPath web products, such as Orchestrator, Insights, or Action Center. Each service does a unique job in the automation process. The services can be assigned to a tenant for their individual automation needs.
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. User accounts: Individual users with unique access based on assigned roles and licenses. Robot accounts: Used to run automated processes and have special permissions based on robot's role and automation requirements. Groups: Collections of users who share the same access, permissions, roles, and licenses. External apps: Third-party applications that interact with UiPath, each with its own permissions

User personas

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 Process Mining Developer - Named User
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	Process Mining Business User - Named User Insights Designer User
Tester - tests RPAs and other software within Studio, creates test environments.	Tester - Named User
Automation Express user - designs and runs attended automations for individual needs.	Automation Express

Admin user journey

Admin users are responsible for configuring and managing the platform settings for their organization. They have the authority to define settings, create tenants, manage licenses, and configure accounts and groups. Here's a common journey for admin users during the initial configuration:

Area	Steps
Sign-up/sign in	Create an account and create your organization. Sign in to access your organization.
User interface	Explore the user interface.
Preferences	Customize your account preferences, such as theme, language, and notifications.
Organization settings	Configure organization-specific settings and preferences: manage organization settings; configure authentication settings.
Tenants	Manage tenants to separate different business areas, such as departments, geographical locations, business units, etc.
Services	Manage services for each tenant.
Access control	Set up user accounts, groups, and permissions for efficient collaboration and access control. You can use preconfigured groups and roles that for managing access and permissions. You can also create custom groups and roles. Create accounts, add them to groups to grant permissions, and also allocate user licenses. manage the accounts and groups for your organization manage access
Licensing	Manage licensing for the entire organization, individual tenants, and users: allocate robot and service licenses to tenants allocate user licenses

Non-admin user journey

Non-admin users are focused on using the platform's services to accomplish their tasks. They don't typically have administrative privileges but need to effectively utilize the platform's features.

Here's a common journey for non-admin users:

Area	Steps
Sign-up/sign in	Sign in to access the platform via SSO.
User interface	Explore the user interface.
Preferences	Customize your account preferences, such as theme, language, and notifications.
Services/Products	Access and utilize services within the platform according to your role and tasks.