Setting up Attended Robots

Note:

Learn the fundamentals ofattended robots.

Robots in modern folders run under certain accounts - user or robot accounts - meaning robots run in the context of the identities corresponding to those accounts. Those 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.

End-to-end Attended Setup

1. Create a machine template or a standard machine. For personal workspace accounts, a machine template is automatically created.

   Where from?

   Tenant > Machines

   See here how to create a machine.

2. Connect UiPath Assistant to Orchestrator using the key generated by the machine entity.

   Where from?

   UiPath Assistant > Orchestrator Settings

   See here how to connect the UiPath Robot to Orchestrator.

3. Configure the account: set its role at the tenant level, enable automatic robot creation, select the license type, select the Stand-alone checkbox if your Studio/StudioX/StudioPro is locally licensed such that Orchestrator doesn't allocate a license from its licenses pool, set the username used to log on to the machine on which the UiPath Robot is installed, configure the execution settings of the UiPath Robot.

   Where from?

   Tenant > Manage access > Assign roles

   See here how to manage roles.

4. Assign the account to one or multiple folders while choosing the appropriate roles at the folder level. Personal workspace users can work in the context of their own workspace directly.
   Important: This gives access to that folder and makes the processes deployed there available and ready to get executed.

   Where from?

   Tenant > Folders

   See here how to assign accounts to a folder.

5. Start a job.

   Where from?

   UiPath Assistant

In attended mode, the UiPath Assistant shows the processes across all the folders the account is assigned to.

These processes cannot be started or triggered in unattended mode from Orchestrator unless it's for debugging purposes. See Studio design and Orchestrator debugging.

Setting up Attended Robots for Groups

This procedure walks admins through the steps for enabling attended robots for a group of users. Groups are used to simplify administration for accounts with similar access, robot configuration, and licensing needs, that are managed together.

1. Reference a group in Orchestrator or edit an existing group and assign roles to it.
2. On the Robot setup tab, enable the toggle for the attended robot.
3. On the Robot settings tab, configure execution settings for the corresponding UiPath Robot.
4. Click Add. The group is referenced/updated. One attended floating robot is provisioned for each group member that signs into Orchestrator. An attended license is consumed by each user. Licenses are allocated on a first-come-first-served basis. If you want a license assigned to a different user, you must manually free one up by deallocating it from an existing user.

Setting up Attended Robots for Individual Accounts

This procedure walks admins through the steps for enabling attended robots for individual user accounts. This is recommended if group members require additional capabilities on top of those granted by group membership and it helps achieve granular control in terms of robot configuration.

1. Add or edit a user account and assign roles to it.
2. On the Robot setup tab, enable the toggle for the attended robot.
3. On the Robot settings tab, configure execution settings for the corresponding UiPath Robot.
4. Click Add. The user account is created/updated. One attended floating robot is created for the user.