orchestrator

latest

false

Getting started
- Introduction
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- 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
- Folders
- Monitoring
- Access control
  - Account types
  - Default roles
    - Robot role
    - Standard roles
      - Automation Developer
  - Managing custom roles
  - Configuring access for accounts
- Configuring automation capabilities
  - Enabling personal automations
    - Enabling individual users to run personal automations
- Machines
- Packages
- Audit
- Credential Stores
  - Integrating credential stores
  - Managing credential stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
  - Robot Security Tab
  - Scalability Tab
    - SignalR (Robots)
Cloud robots
- Automation Cloud™ Robots - VM
- Configuring VPN for cloud robots
- My notifications
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
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- 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
Monitoring
- About Monitoring
- Machines
- Processes
- Queues
- Queues SLA
Queues
- About Queues and Transactions
- 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
Test Suite - Orchestrator
- 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
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Authentication
- About Authentication
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Classic Robots
- Robots
- Environments
  - Managing Environments
- Jobs
- Triggers
- Monitoring
  - Robots
- Resources
Troubleshooting
- About Troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator User Guide

DELIVERY:

Automation Cloud Automation Cloud Public Sector Automation Suite Standalone

Last updated Nov 20, 2024

Default roles

This page displays the permissions included for each default role in Orchestrator.

You can view and edit the permissions for each role from the Roles page by clicking the More Actions icon on the right end of a row.

If a role cannot be edited, you have the option to duplicate and customize it as a new role instead (not available for mixed roles).

Administrator role

A role that has all tenant- and folder-level permissions.

This is a mixed role and includes both tenant and folder permissions. With mixed roles, for a global operation, only the user's tenant permissions are taken into consideration; for a folder-specific operation, if a custom role is defined, folder permissions are applied in favor of any tenant permissions present.

It includes the following permissions, which cannot be changed.

Tenant permissions

Folder permissions

Robot role

Important:

This role is no longer available for new tenants. To replicate its permissions, use the following role combination:

Allow to be Automation User at the tenant level
Automation User at the folder level

The Robot role can still be used in any existing tenants.

All permissions required to execute processes.

Note: As robot accounts can write logs without the explicit assignment of the Create permission on Logs, Orchestrator skips the check on this permission.

By default, the role has the following permissions, which can be changed.

Tenant pemissions

Folder permissions

Personal Workspace Administrator role

This is a folder role and it includes the following permissions by default, which cannot be edited.

Standard roles

The following roles are pre-configured with the permissions for the tenant level or the folder level that are required to work in folders.

These roles cannot be changed, but you can duplicate and customize them as a new role if needed.

Below you can see the permissions granted for each standard role.

Orchestrator Administrator

This role is granted all tenant-level permissions, and should be assigned at the tenant level to any users in charge with the management of all tenant entities.

We recommend this role over Administrator, which is not relevant in a modern folder infrastructure.

This is a tenant role and includes the following permissions by default, which cannot be changed.

Allow to be Folder Administrator

A role with the minimum tenant-level permissions needed to manage their own folders and subfolders.

Accounts that have the Allow to be Folder Administrator tenant role should also have the Folder Administrator folder role assigned to them at the folder level.

This is a tenant role and includes the following permissions by default, which cannot be changed.

Folder Administrator

A user with the minimum folder-level permissions needed to manage their own folders and subfolders.

Accounts that have the Folder Administrator folder role should also have the Allow to be Folder Administrator tenant role assigned to them at the tenant level.

This is a folder role and includes the following permissions by default, which cannot be changed.

Allow to be Automation User

A user with the minimum folder level permissions needed to execute processes from Assistant, as well as unattended automations.

Accounts that have the Allow to be Automation User tenant role should also have the Automation User folder role assigned to them at the folder level.

This is a tenant role and includes the following permissions by default, which cannot be changed.

Automation User

A user with the minimum folder level permissions needed to execute processes from Assistant, as well as unattended automations.

We recommend that accounts that have the Automation User folder role also have the Allow to be Automation User tenant role assigned to them at the tenant level.

This is a folder role and includes the following permissions by default, which cannot be changed.

Allow to be Automation Publisher

A user who can publish processes to Orchestrator.

This role can be assigned on top of Allow to be Automation User to allow a user to both publish and execute a process.

Accounts that have the Allow to be Automation Publisher tenant role should also have the Automation Publisher folder role assigned to them at the folder level.

This is a tenant role and includes the following permissions by default, which cannot be changed.

Automation Publisher

A user who can publish processes to Orchestrator.

This role can be assigned on top of Automation User to allow a user to both publish and execute a process.

Accounts that have the Automation Publisher folder role should also have Allow to be Automation Publisher tenant role assigned to them at the tenant level.

This is a folder role and includes the following permissions by default, which cannot be changed.

Allow to be Automation Developer

A user who creates automation projects, but does not have direct access to complex and expensive resources, such as storage buckets.

Accounts that have the Allow to be Automation Developer tenant role should also have the Automation Developer folder role assigned to them at the folder level.

This is a tenant role and includes the following permissions by default, which cannot be changed.

Automation Developer

A user who creates automation projects, but does not have direct access to complex and expensive resources, such as storage buckets.

Accounts that have the Automation Developer folder role should also have the Allow to be Automation Developer tenant role assigned to them at the tenant level.

This is a folder role and includes the following permissions by default, which cannot be changed.