orchestrator
2022.10
false
- Getting started
- Best practices
- Tenant
- 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)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Assigning Roles
- Managing Roles
- Default Roles
- FAQ
- 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
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Configuring Robot Accounts to Run Unattended Automations
Orchestrator User Guide
Last updated Oct 9, 2024
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.