# 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, as described in the following table:

## 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, as described in the following table:

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
     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: Admin users are not mapped based on their user licenses but based on their membership in the **Administrators** user group.
* Non admin users: Non-admin users are mapped based on their user licenses.

### 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. The following table describes a common journey for admin users during the initial configuration:

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
     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 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.

The following table describes 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](https://docs.uipath.com/test-cloud/automation-cloud/latest/admin-guide/managing-user-preferences#managing-user-preferences), such as theme, language, and notifications. |
| **Services/Products** | Access and utilize services within the platform according to your role and tasks. |