- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read Only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Assigning Roles
- Managing Roles
- Default Roles
- Configuring Access for Accounts
- Enabling Users to Run Personal Automations
- Enabling Users to Run Automations on Unattended Infrastructure Via Unattended Robots
- Configuring Robot Accounts to Run Unattended Automations
- Audit
- Settings
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. Learn about access control 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
To configure unattended execution settings under a certain robot account and on specific infrastructure, an administrator must do the following when referencing or editing the robot account in Orchestrator: