robot

2023.4

false

Getting Started
- Introduction
- Setting Up Interactive Sign-In
Installation and Upgrade
- About Backward and Forward Compatibility
- Hardware and Software Requirements
- Installing the Robot
  - Deployment guidelines
  - AWS Deployment
  - Azure Marketplace Deployment
  - Deploying unattended automations
- Updating the Robot
- Setting Up Windows Server for High-Density Robots
- Services the Robot Connects to
- Configuration files
Robot Types
- According to License
- Attended Vs Unattended Robots
- High-Density Robots
- Linux Robots
Robot Components
- Robot Service
- Robot Executor
- Command Line Interface
Licensing
- Licensing a Robot
- LicenseTool Command Descriptions
Connecting Robots to Orchestrator
- Interactive Sign In
Processes and Activities
- About Automation Projects on the Robot
- About the Activities Feeds
- Background Process Automation
- Robot API
- Package Signature Verification
Logging
- Robot Logs
- Logging and Log Levels
Specific Scenarios
- Windows Sessions
- Implementing authentication with credential providers
- Redirecting Robots Through a Proxy Server
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike integration
- Robot Citrix Apps Virtualization
Governance
- Settings for Robot Policies
Troubleshooting
- Robot Service troubleshooting
- Execution troubleshooting
- Recording and Remote Control troubleshooting
- Networking troubleshooting
- Connection troubleshooting
- Licensing troubleshooting
- Package troubleshooting
- .NET troubleshooting
- Logging troubleshooting
- Session troubleshooting
- CrowdStrike integration troubleshooting

Robot Admin Guide

Last updated Feb 6, 2026

Introduction

The Robot is UiPath’s execution agent that enables you to run processes developed in Studio. Robots need to be connected to Orchestrator in order to execute processes or they have to be licensed locally (read more about licensing). The type of Robot you have at your disposal is determined by the license, while the Robot service is determined by the deployment.

The Robot is split into several components, each being dedicated to a particular task in your automation. The Robot components are as follows:

Having the Robot components split as explained above helps developers, support users, and computers easily run, identify, and track what each component is executing. Special behaviors can be configured per component this way, such as setting up different Firewall rules for the Executor and the Service.

The Robot can open interactive Windows sessions, under the Local System account, and has all the rights of a Windows service. Learn more about Windows sessions.

Installing the Robot using UiPathStudio.msi deploys the Service Mode Robot by default. It can also be installed from the Command Prompt, as explained on this page.

Robots can also be installed in User Mode. For your Robot, this means that it has the exact same rights as the user under which it has been installed.

Both the Service Mode and User Mode Robots can be configured as HD Robots.

Please note that packages downloaded by the Service Mode Robot cannot be run by User Mode Robots. This is because the Service Mode Robot downloads packages in the Local System (not the local user), and the User Mode Robot does not have permissions for that folder. If this happens, it is recommended to delete all packages downloaded by the Service Mode Robot, which are located in the %userprofile%\.nuget\packages folder.

Regardless of the mode in which you installed the Robot, it can still be connected to Orchestrator.

Was this page helpful?

NEXTSetting Up Interactive Sign-In