- Getting started
- Introduction
- User Options
- Resetting Your Password
- My Profile
- 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
- Organizing Resources With Tags
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- 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
- Folders
- Managing Folders
- Classic Folders Vs Modern Folders
- Migrating From Classic Folders 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
- FAQ
- Machines
- Managing Machines
- Assigning Machine Objects to Folders
- Configuring Account-machine Mappings
- Packages
- Managing Packages
- About Libraries
- Managing Libraries
- Audit
- Credential Stores
- Managing Credential Stores
- CyberArk® CCP Integration
- Azure Key Vault Integration
- HashiCorp Vault Integration
- BeyondTrust Integration
- Webhooks
- Types of Events
- Managing Webhooks
- Licensing
- Managing Your Licenses
- Alerts
- Setting Up Alert Emails
- Settings
- General Tab
- Deployment Tab
- Robot Security Tab
- Scalability Tab
- Non-Working Days Tab
- 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
- About Recording
- Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Triggers
- About Triggers
- Managing Triggers
- Using Cron Expressions
- Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
- 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
- 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)
- 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
- 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
- Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide
Orchestrator uses an access-control mechanism based on roles and permissions. Roles are collections of permissions meaning that the permissions needed to use certain Orchestrator features are included in roles.
For example, here's a custom role where you can see some of the permissions it includes:
When creating a role, you can start from scratch and create a custom role, or you have the option to import a role.
Creating a Custom Role
The role is now available and you can add one or multiple users who need the set of permissions that this role provides by following the instructions below.
Importing a Role
You can base a new role on a role you already have, even if the base role is in a different organization or tenant. If you export the base role, you can import it to any tenant and, if needed, customize it.
The new role is now available on the Roles page and you can assign it to accounts or groups as needed.
These instructions are for assigning tenant roles.
If you need to assign a folder role, you can:
- go to Tenant > Folders and then select the folder where you want to assign the role
- select the folder in the left pane to switch to folder context and then go to the Settings page for that folder.
Changes to roles apply immediately when a user logs in, or automatically within one hour.
Changes to roles apply immediately when a user logs in, or within one hour if the user is already logged in.
You cannot remove any of the default roles, you can only remove custom roles.
- Go to Tenant > Manage access and select the Roles tab.
- Click More Actions at the right end of the row and select Manage Users.
- Review the users who has this role assigned and make sure you reassign them to a different or similar role if needed before deleting the role.
- Click More Actions at the right end of the row and select Remove.
If you want to recreate a particular role in a different organization or tenant, you can export the role as a CSV file and then import it in the target Orchestrator tenant.
To export a role as a CSV file:
You can now use this file to import the role into any Orchestrator tenant.
The CSV file is intended to be used strictly for importing back into Orchestrator in the form in which it was exported. Editing the file in any way can result in import errors.
If you need to make changes to the exported role, you have the option to do so during the import process.