UiPath Documentation
robot
2026.10
false
Robot admin guide

Attended vs. unattended

Differences between attended and unattended Robot automation, with a lookup of which settings, requirements, and pages apply to each.

The first decision to be made when planning your automations is whether the solution is to be executed in an attended or unattended context. While both types are intended to automate tasks a user would otherwise perform manually on their computer, the specific use cases are different between them.

  • Attended automation runs on a person's own machine, started and supervised by that person. For details, refer to Attended automations.
  • Unattended automation runs on its own, started by Orchestrator, a trigger, or another automation. For details, refer to Unattended automations.

Most pages in this guide apply to both. Where installing, connecting, or running the Robot differs, the page says so in a section or a table. The following table lists every difference and the page that covers it.

What applies to attended and unattended robots​

AreaAttended robotsUnattended robotsPage
Install modeUser mode: a per-user installation, or a per-machine installation with the Attended robot typeService mode: a per-machine installation with the Unattended robot typeInstalling the Robot
Connecting at install timeAutomatically sign in, with the Service URLClient Id and Client Secret, with the Service URLInstalling the Robot
Windows prerequisitesNone beyond the machine requirementsThe account that runs jobs is in Remote Desktop Users and has the logon rightsPrerequisites
Connecting to OrchestratorInteractive sign-in, recommended, or client credentialsClient credentialsConnecting the Robot to Orchestrator
LicensingA user license that includes the attended robot: Basic, Plus, Pro, or App Test Developer in Unified Pricing; Attended, Citizen Developer, or Automation Developer in FlexRuntimes for RPA processes and test cases. Functions and API workflows use an unattended runtime or units. Agents use units only, pay as you go.Licensing the Robot
Agents, functions, and API workflowsNot supportedSupported on Windows, for robots connected with client credentialsEnabling agents, functions, and API workflows
Windows sessionThe signed-in user's sessionThe Robot opens a console or RDP session for each jobWindows sessions
High-Density RobotsNot supportedSupported on Windows Server, in service modeHigh-Density Robots
Preloaded executionAvailableNot available. Preloaded executors exist only in user mode.Configuring preloaded execution
ProxyConfigured for the user who runs the RobotConfigured for the Robot serviceRedirecting robots through a proxy server
Entra ID users with multifactor authenticationNot applicableSupported for the account that runs jobsUsing EntraID users with MFA
RobotJS add-onSelected by default at installationCleared by default at installationInstalling the Robot
UpdatesA notification. The user can postpone, up to the period your update policy sets.Installed between jobs, with no notificationUpdating the Robot
Operating systemsWindowsWindows and LinuxWorkload support by operating system
  • What applies to attended and unattended robots​

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated