- Getting started
- Best practices
- Tenant
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Host administration
- Identity Server
- Authentication
- Organization administration
- Other Configurations
- Integrations
- Classic Robots
- Troubleshooting
Robots
Robots in modern folders run under a user profile, meaning robots always run in the context of certain user identities. User identities and their association with roles allow for a certain level of access to resources in Orchestrator. A user gets the permissions required to perform particular operations through one or multiple roles.
Because attended robots impersonate real individuals, they should run under user accounts. Unattended robots should run under robot accounts, special service accounts dedicated to applications or virtual machines, not persons.
Robot management is performed on the Users page and involves enabling automatic robot creation for the desired user identity. The robot is automatically created according to your settings. Robot management is done automatically, i.e., enabling automatic robot creation at the user level, defining its execution settings and authentication credentials, and automatically creating a floating robot.
UiPath Robot has access to the resources residing in the folders the user (and machine for unattended) has access to.
Attended robots (or unattended used in attended mode) can be monitored at the tenant level on the Robots page. Unattended machines and runtimes can be monitored at the folder level (Monitoring > Machines).
Automatic robot management can be configured for directory users or directory groups as well. The automatic robot provisioning setting for a directory group added to Orchestrator is inherited by any user member of that AD group. Robot auto-provisioning is only valid for attended robots.
The Robots page at the tenant level illustrates the robot configuration done in Orchestrator and how this maps to your attended and unattended scenarios. There are four separate tabs where you can choose the context you are interested in.
This section shows the robot configuration made in modern folders. Specifically, it offers a breakdown of all robots created for your users, by enabling the Automatically create an attended robot for this user and/or Automatically create an unattended robot for this user options.
Column Name |
Description |
---|---|
User |
The username of the user under whom the robot runs. |
Domain\Username |
The domain\username of the user under whom the robot runs. |
Type |
The robot type (attended, unattended) as enabled for the user in Orchestrator alongside the license type, in parentheses. |
This section offers an overview of all unattended sessions and related information.
Column Name |
Description |
---|---|
Connected Machine |
The name of the host machine. |
Machine |
The machine template used to connect the corresponding host machine to Orchestrator. |
Runtimes |
The number of runtimes associated with a machine template. Each host machine connected using that machine template secures this number of licenses from the tenant's pool of licenses. |
In Use |
The number of runtimes currently being consumed out of the number of runtimes secured on that host machine. A runtime is consumed during job execution. |
License Type |
The type of license. |
Service Username |
The identity under which unattended jobs are executed. For service accounts, this is empty. |
Status |
The connection status of each host machine. |
Last Heartbeat |
Time elapsed since the last heartbeat. Hover over this field to see the exact time of the last heartbeat. |
Version |
The Robot version. |
This section offers an overview of all user sessions started from the Assistant and related information.
Column Name |
Description |
---|---|
User |
The username of the user under whom the robot runs. |
Domain\Username |
The domain\username of the user under whom the robot runs. |
Connected Machine |
The name of the host machine on which the robot resides. |
Status | |
Type |
The robot type alongside the license type, in parentheses. Starting an Assistant session on a machine used for unattended purposes displays Unattended as the type. |
Version |
The Robot version. |