orchestrator
latest
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
- Managing Folders
- Organizing Folders
- Personal Workspaces
- Managing Personal Workspaces
- Configure the Default Execution Identity
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Registry
- Cloud robots
- Automation Suite Robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
The Default Execution Identity setting lets Orchestrator automatically assign a specified account and machine to every new root folder and solution folder created in the tenant. Configuring this setting removes the need for per-folder robot and machine setup when new folders are created.
Prerequisites
- You have administrator access to the Orchestrator tenant.
- At least one robot account with the Automation User role exists in the tenant.
- At least one machine template exists in the tenant.
Configure the Default Execution Identity
- In Orchestrator, navigate to Tenant and select Settings.
- Locate the Default Execution Settings section.
- In the account field, select the account to assign as the default execution identity for new root folders.
- In the machine field, select the machine template to assign to new root folders.
- To extend machine access to subfolders of new root folders, enable the propagate-to-subfolders option.
- Select Save to apply the settings.
Result
New root folders and solution folders created in the tenant are automatically assigned the configured account and machine. Developers can deploy and run automations in new folders without additional account or machine setup.
If the configured account or machine is later deleted, Orchestrator automatically removes the deleted entry from the Default Execution Identity configuration.