Orchestrator user guide

DELIVERY:

Last updated Jul 1, 2025

Configuring robot accounts to run unattended automations

Unattended automation typically runs on robot accounts, the UiPath® equivalent of Windows service accounts. Robot accounts can be thought of as non-human identities that need to be authorized to access Orchestrator resources. Their association with roles allows for a certain level of access to resources in Orchestrator.

Robot accounts have their unattended capabilities enabled by default, administrators only have to configure several infrastructure related settings.

Enabling unattended automation on a robot account

Configure unattended execution settings under a robot account and on a specific infrastructure as follows:

Under Manage Access - Access Rules, select Robot accounts.
Then, either select Assign robot account, to assign a new robot account and add roles, or edit an existing robot account.

On the Assign access rules page, under Unattended setup, select the infrastructure to execute unattended foreground processes under that robot account:

Select the Unattended robot using predefined VM credentials (for runs on UiPath Automation Cloud robots only) option to delegate Automation Cloud robots for executing processes that require user interaction. The robots use a preconfigured Windows account when they execute processes.
Select the Unattended robot using custom Windows credentials option.

Next, to execute processes on a specific Windows machine, fill in the Domain\Username and Password fields.

You must specify the correct credentials for the host machine, so the robot can log into it successfully. This allows the robot to run processes that require user interaction under that specific Windows account. For more details on how to retrieve your Windows credentials, check How to find my computer credential information in Windows 10.

To configure the credential settings when you use specific Windows accounts, check the following:

Field	Description
Domain\Username	The account under which the robot runs. For domain-joined accounts, use the `domain\username` syntax. For example `deskover\localUser1`. For local Windows accounts, use the `host_machine_name\username` syntax, with the name of the host machine, instead of the domain. For example, `LAPTOP1935\localUser2`. For local Windows accounts residing on multiple host machines, that you want to use regardless of the machine, use the `.\username` syntax with a dot instead of the host machine name. For example `.\localUser3`. For Azure AD joined machines, use the `azuread\[email protected]` syntax.
Credential store	The credential store used for your password. For more details, check the Credential stores page.
Password	The password used to log into the machine where UiPath Robot is installed.
Credential type	Specifies the type of password credential.

Note: Unattended robots can run background jobs on any infrastructure. It is, however, recommended to specialize your host machines to execute particular types of processes in order to maximize efficiency and cut costs. Learn more about how to optimize unattended infrastructure using machine templates.

Enable the Run only one job at a time option to restrict the account to simultaneously execute multiple jobs. This helps when you automate applications that do not allow you to use a credential more than once at a time (e.g., SAP).
Under Advanced robot options, configure execution settings for the unattended robot. Learn about robot settings.
Select Update.

On this page

Enabling unattended automation on a robot account

Was this page helpful?

PREVIOUSEnabling unattended automations

NEXTMachines

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy