Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

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. Learn about access control in Orchestrator.

Because attended robots impersonate real individuals, they should run under user accounts. Unattended robots should run under service accounts, special accounts dedicated to applications or virtual machines, not persons.

Robot Management


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.

Robot View


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.

A. Configured robots

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.

1964
Column NameDescription
UserThe username of the user under whom the robot runs.
Domain\UsernameThe domain\username of the user under whom the robot runs.
TypeThe robot type (attended, unattended) as enabled for the user in Orchestrator alongside the license type, in parentheses.

B. Unattended sessions

This section offers an overview of all unattended sessions and related information.

1957
Column NameDescription
Connected MachineThe name of the host machine.
MachineThe machine template used to connect the corresponding host machine to Orchestrator.
RuntimesThe 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 UseThe 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 TypeThe type of license.
Service UsernameThe identity under which unattended jobs are executed. For service accounts, this is empty.
StatusThe connection status of each host machine.
Last HeartbeatTime elapsed since the last heartbeat. Hover over this field to see the exact time of the last heartbeat.
VersionThe Robot version.

C. User sessions

This section offers an overview of all user sessions started from the Assistant and related information.

1981
Column NameDescription
UserThe username of the user under whom the robot runs.
Domain\UsernameThe domain\username of the user under whom the robot runs.
Connected MachineThe name of the host machine on which the robot resides.
StatusThe status of the attended robot.

Known Issue: Attended robots running jobs appear as Available if the Assistant is refreshed.
TypeThe robot type alongside the license type, in parentheses. Starting an Assistant session on a machine used for unattended purposes displays Unattended as the type.
VersionThe Robot version.

D. Classic robots

This section offers an overview of robots as defined in classic folders and related information. This tab is not displayed in modern-only organizations.

1970

Updated about a year ago


Robots


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.