robot
2026.10
false
Robot admin guide
- About this guide
- Getting started
- Installing
- Upgrading
- Connecting and licensing
- Configuring
- Running workloads
- RPA processes and tests
- Agents, functions, and API workflows
- Limits
- Securing and governing
- Monitoring
- Troubleshooting
- Reference
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
| Area | Attended robots | Unattended robots | Page |
|---|---|---|---|
| Install mode | User mode: a per-user installation, or a per-machine installation with the Attended robot type | Service mode: a per-machine installation with the Unattended robot type | Installing the Robot |
| Connecting at install time | Automatically sign in, with the Service URL | Client Id and Client Secret, with the Service URL | Installing the Robot |
| Windows prerequisites | None beyond the machine requirements | The account that runs jobs is in Remote Desktop Users and has the logon rights | Prerequisites |
| Connecting to Orchestrator | Interactive sign-in, recommended, or client credentials | Client credentials | Connecting the Robot to Orchestrator |
| Licensing | A user license that includes the attended robot: Basic, Plus, Pro, or App Test Developer in Unified Pricing; Attended, Citizen Developer, or Automation Developer in Flex | Runtimes 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 workflows | Not supported | Supported on Windows, for robots connected with client credentials | Enabling agents, functions, and API workflows |
| Windows session | The signed-in user's session | The Robot opens a console or RDP session for each job | Windows sessions |
| High-Density Robots | Not supported | Supported on Windows Server, in service mode | High-Density Robots |
| Preloaded execution | Available | Not available. Preloaded executors exist only in user mode. | Configuring preloaded execution |
| Proxy | Configured for the user who runs the Robot | Configured for the Robot service | Redirecting robots through a proxy server |
| Entra ID users with multifactor authentication | Not applicable | Supported for the account that runs jobs | Using EntraID users with MFA |
| RobotJS add-on | Selected by default at installation | Cleared by default at installation | Installing the Robot |
| Updates | A notification. The user can postpone, up to the period your update policy sets. | Installed between jobs, with no notification | Updating the Robot |
| Operating systems | Windows | Windows and Linux | Workload support by operating system |