orchestrator
2023.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)
 - Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
 - Deleting Disconnected and Unresponsive Unattended Sessions
 - Robot Authentication
 - Robot Authentication With Client Credentials
 - SmartCard Authentication
 
- Configuring automation capabilities
 - Audit
 - Settings - Tenant Level
 
 - Resource Catalog Service
 - Folders Context
 - Automations
 - Processes
 - Jobs
 - Triggers
 - Logs
 - Monitoring
 - Queues
 - Assets
 - Storage Buckets
 - Orchestrator testing
 - Other Configurations
 - Integrations
 - Host administration
 - Organization administration
 - Troubleshooting
 

Orchestrator user guide
Last updated Sep 3, 2025
Note: Make sure you have configured the AWS Secrets Manager integration.
            
            
            
            To store an unattended robot password in the read-only version of AWS Secrets Manager, create a secret in AWS, using the Other type of secret option.
This needs to include a Value key, whose value represents the robot password.
In the AWS Secrets Manager console, these key/value pairs can also be stored as a JSON string: