- Getting started
- Introduction
- User options
- Logging in to Orchestrator
- Resetting your password
- Robots
- Robot Statuses
- Robot Settings
- Auto Updating Client Components
- Orchestrator Configuration Checklist
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Useful concepts in unattended automation
- How is unattended automation performed
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- 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
- Folders
- Managing Folders
- Classic Folders Vs Modern Folders
- Migrating From Classic to Modern Folders
- Administration of Modern Folders
- Personal Workspaces
- Managing Personal Workspaces
- Monitoring
- Unattended sessions
- User sessions
- License
- Managing Access and Automation Capabilities
- Assigning Roles
- Managing Roles
- Default roles
- Configuring access for accounts
- Enabling personal automations
- Enabling unattended automations
- Configuring robot accounts to run unattended automations
- Machines
- Managing Machines
- Assigning Machine Objects to Folders
- Configuring Account-machine Mappings
- EDR Protection Status
- Packages
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Credential Stores
- Managing credential stores
- Integrating credential stores
- Webhooks
- Types of Events
- Managing Webhooks
- Licensing
- Managing Your Licenses
- Alerts
- Configuring Alerts
- Alert Emails
- Setting up Alert Emails
- Settings - Tenant Level
- Resource Catalog Service
- About Resource Catalog Service
- Folders Context
- About the Folders Context
- Home
- Automations
- About Automations
- Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Troubleshooting Jobs
- Triggers
- About triggers
- Time triggers
- Queue triggers
- Managing triggers
- Creating a Time Trigger
- Creating a Queue Trigger
- Managing Non-Working Days
- Using Cron Expressions
- Triggering jobs on the last day of the month
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- Orchestrator Logs
- Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
- Exporting usage data
- Queues
- About Queues and Transactions
- Queue Item Statuses
- Business Exception Vs Application Exception
- Studio Activities Used With Queues
- Queue Item Retention Policy
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
- Editing Transactions
- Field Descriptions for the Transactions .csv File
- Review Requests
- Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
- Storage Buckets
- About Storage Buckets
- CORS/CSP Configuration
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
- Orchestrator testing
- Test Automation
- Test Cases
- Field Descriptions for the Test Cases Page
- Test Sets
- Field Descriptions for the Test Sets Page
- Test Executions
- Field Descriptions for the Test Executions Page
- Test Schedules
- Field Descriptions for the Test Schedules Page
- Test Data Queues
- Managing Test Data Queues in Orchestrator
- Managing Test Data Queues in Studio
- Field Descriptions for the Test Data Queues Page
- Test Data Queue Activities
- Testing Data Retention Policy
- Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
- Integrations
- About Input and Output Arguments
- Example of Using Input and Output Arguments
- Classic Robots
- Robots
- Managing Robots
- Robot Statuses
- Setup Samples
- Environments
- Managing Environments
- Jobs
- Triggers
- Monitoring
- Robots
- Resources
- Host administration
- About the host level
- Managing system administrators
- Managing tenants
- Configuring host authentication settings
- Reconfiguring authentication after upgrade
- Allowing or restricting basic authentication
- Configuring SSO: SAML 2.0
- ADFS Authentication
- Google Authentication
- Okta Authentication
- PingOne Authentication
- Custom Mapping
- Self-signed Certificates
- Private Key Certificates
- Configuring SSO: Google
- Configuring SSO: Microsoft Entra ID
- Configuring the Active Directory Integration
- Switching between Active Directory adapters
- Managing your host license
- Allocating Licenses to Tenants
- Configuring system email notifications
- Configuring other host settings
- Customizing the Login page
- Session Policy
- Orchestrator Host Settings
- Audit logs for the host portal
- Maintenance Mode
- Organization administration
- About organizations
- Managing organization administrators
- Managing organization settings
- Configuring organization authentication
- Allowing or restricting basic authentication
- Setting up the Azure AD integration
- Configuring the SAML integration
- Configuring organization security
- Session policy
- Restricting access to a set of users
- About licensing
- Activating your license
- Accounts and groups
- Managing access
- Managing accounts and groups
- Authorizing external applications
- Managing external OAuth applications
- Configuring fine-grained access for confidential apps
- Managing tags
- Overriding system email settings
- Email setup
- System emails are not sent - SslHandshakeException
- Audit logs
- Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors
Orchestrator user guide
An environment is a grouping of Robots that is used to deploy processes.
The Environments page displays all previously created environments and enables you to manage Robots within them.
To access the Environments page, click the Environments tab in the Robots page.
Use meaningful names and descriptions for each environment created.
Orchestrator Environments should map the groups of process execution. Each environment should have a specific role in the company's business logic.
If a Robot is going to execute two different roles, it can be assigned to multiple environments. If you have multiple Robots on the same machine, it is recommended that you group them in the same environment. Otherwise, some errors might occur when deploying different versions of the same process.
Access management between Robots and processes is done by using Environments properly.
It is good practice to assign each package published to Orchestrator to an environment. The deployment decision is taken in the Processes page. All the Robots from the environment get access to the package version set for this process.
When a new version of a process is available, an icon informs the user.
Rolling back to the previous version is always an option if something goes wrong after updating. This can be done by pressing the Rollback button.