- 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
- Audit
- Settings
Managing Roles
About Roles
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:
For more information about roles, see Managing access and automation capabilities.
Deciding which permissions to include
Each role is a combination of permissions which control the program areas and actions that accounts with the role can access.
Example: A role called Infra, which is intended for the person managing the VMs you use for automation, may include permissions such as Machines - View, Machines - Edit, Machines - Create, and Machines - Delete, as well as other permissions that are relevant for their job.
When creating or editing a role, you must review the list of available permissions and decide which ones to include or not. Here are some approaches that you can try:
- Start from our default roles: Orchestrator comes with default roles for the most common automation user types, such as the Administrator role, Automation User, and more. You can either use these roles, or duplicate the one that is closest to what you need, and then customize it.
- Create a custom role: When creating a role, you are presented with a list of all available permissions for the tenant or folder level, depending on the role type, and you must decide which ones to include or not.
Viewing permission information
While creating or editing a role, you can hover over the checkbox of a permission to see to which Orchestrator pages the permission allows access. The information can help you broadly decide if to include the permission or not.
- The functions of permissions can be more complex than only access to and abilities within the context of a page. When in doubt about what permissions are necessary for a task, check the documentation for that task for detailed permission requirements.For advanced users, you can also check the Orchestrator API Swagger, which includes information about the required permissions for each operation. For instructions see Accessing the Swagger file.
- The information that is displayed
for each permission only covers Orchestrator pages. It does not cover pages or
actions in other UiPath services.
For example, you may see that no pages are blocked by the ML Skills permissions, meaning that the permission has no effect in terms of access to Orchestrator pages. But granting permissions for ML Skills is necessary for using UiPath AI CenterTM. In this case, you must check the AI Center documentation for more information about the ML Skills permissions.
Creating a Role
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.
Editing a Role
Changes to roles apply immediately when a user logs in, or within one hour if the user is already logged in.
Removing a Role
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.
Exporting a Role
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.