- 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
- Configuring automation capabilities
- Audit
- Settings
- Cloud robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Orchestrator testing
- Resource Catalog Service
- Authentication
- Integrations
- Classic Robots
- Troubleshooting

Orchestrator user guide
Unattended automation is a process whereby machines perform tasks on their own, without the need for human intervention. Such tasks are usually:
-
complex
-
repetitive
-
carried out in batches on large amounts of data
And with the help of unattended automation, they become:
-
fast
-
scalable
-
reiterative
-
immune to errors
-
inexpensive
-
able to be run around the clock
Important: Unattended automation requires elevated permissions, access levels, and credentials, which makes it best suited for highly privileged operations.
Unattended automation is performed by unattended robots, which are deployed from Orchestrator and are programmed to execute based on a certain configuration. They run in the back-end, on dedicated machines, so users never need to interrupt their work to trigger a process.
This option is available to you if you meet the following permission criteria:
-
Role permissions
-
Machines - View, Create, and Edit
-
Users - View, Create, Edit, and Delete
-
Robots - View, Create, and Edit
-
-
Organization Administrator role - this is needed in order to create an account at the organization level and assign it to the Everyone group.
- Tenant Administrator role - this is needed to create robot accounts from the
Unattended setup page.
Note: If the Create new robot account button is disabled during the unattended setup flow, the current user likely does not have sufficient permissions. In addition to the Orchestrator role permissions listed above, the user must have the Tenant Administrator role in the tenant to create robot accounts.
-
At least one of these four action combinations:
-
You have permission to view and edit robot units.
-
You have permission to view robot units and edit subfolders.
-
You have permission to view subfolders and edit robot units.
-
You have permission to view and edit subfolders.
-
Roles
The following roles are automatically allocated:
-
When creating a robot account, the Allow to be Automation User tenant role is allocated.
-
When selecting a folder, the Automation User folder role is allocated.