- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Assigning Roles
- Managing Roles
- Default Roles
- Audit
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Identity Server
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
Assigning Roles
The Assign roles tab of the Manage access page lets you search for users and groups that already exist at the organization level and configure permissions for them in Orchestrator.
To assign roles
- Go to Tenant > Manage access.
-
Click Assign roles, and select User,Robot account, or Group.
The Assign roles window opens.
- Follow the applicable instructions:
If you assign roles to a group, those roles are inherited by all users who are part of that group.
We recommend that you maintain access by assigning roles to groups and then assigning accounts to the right groups to grant them the roles they need.
However, if you need to perform a one-time role assignment for a specific account, you can assign roles directly to the account, as described below.
- Go to Tenant > Manage Access > Assign roles tab.
- In the top right of the tab, click Assign roles and select User.
- Go to Tenant > Manage Access > Assign roles tab.
- In the top right of the tab, click Assign roles and select Robot account.
- Go to Tenant > Manage access > Assign roles tab.
- At the right end of the row, click More Actions and select Edit.
- Make changes as needed.
- When finished, click Update to apply your changes.
Deactivated users can no longer access Orchestrator.
Removing a user or group from Orchestrator does not delete the account from your organization.
- Go to Tenant > Manage access > Assign roles tab.
- At the right end of the row, click More Actions and select Remove.
- Confirm the operation.
The account or group is removed from Orchestrator and all roles are revoked.
Alternatively, select one or multiple accounts, and click Remove.
Optimizing resource consumption and maximizing execution capacity in modern folders involves little to no control over how users are allocated to jobs. For scenarios where a credential cannot be used more than once at a time (for example, with SAP), you can limit concurrent execution for unattended processes. This helps modulate the job allocation algorithm by restricting a user from simultaneously executing multiple jobs.
- Assigning Roles to a Group
- 1) General Details
- 2) Robot Setup
- Assigning Roles to an Account
- 1) General Details
- 2a) Attended Robot
- 2b) Unattended Robot
- 3) Robot Settings
- Assigning Roles to a Robot Account
- 1) General Details
- 2) Robot Setup
- 3) Robot Settings
- Checking Roles
- Editing Roles
- Activating or Deactivating an Account
- Removing an Account or Group
- Disabling Concurrent Execution