Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

Managing Users

Adding Directory Users/Groups


🚧

Important

Adding directory users or groups requires enabled Windows Authentication in your Orchestrator instance.

📘

Note

Group attributes (roles, web login, robot settings) are passed on to any directory user that belongs to that group and is later on manually added or auto-provisioned.

On the Users page, click the Add button, and select Add Directory User or Group. The Add Directory User or Group window is displayed.

User Details

  1. Use the Domain name drop-down to select the Active Directory domain where the user or group resides. You can add domains or subdomains in forests that are 2-way trusted with the domain specified in the WindowsAuth.Domain app setting.

📘

Note

  • It can take up to an hour to update the domain list with newly added two-way trusted domains.

  • Due to various networking or configuration issues, there is a chance that not all domains displayed in the Domain Name drop-down are accessible.

  • Changes made to AD user/group names are not propagated to Orchestrator.

  1. In the Group or Username field, enter the Active Directory group or user you want to add. To refine the search results and improve the search performance in large deployments, it is recommended to select the user type from the User Type drop-down.
  2. From the Roles drop-down, select the role(s) for this user/group.
  3. Use the Allow Web Login toggle to select if this user/group can log in to Orchestrator.
  4. Under UI Profile select the user interface profile for this user/group. Only applicable if personal workspaces are enabled.

Attended Robot

  1. Use the toggle to select whether or not to automatically create an attended robot for the directory user or directory group.
  2. Select the License Type for the robot to be created. Learn about license types.
  3. For licenses that grant Studio/StudioX/StudioPro capabilities (Citizen Developer, RPA Developer, RPA Developer Pro respectively), select the Stand-alone license checkbox if the Studios are licensed locally such that Orchestrator doesn't allocate a license from its pool of licenses.
  4. Select the Automatically create a Personal Workspace for this user checkbox to enable personal workspace creation for that user/group.

Unattended Robot

Not available for directory groups.

  1. Use the toggle to select whether or not to automatically create an unattended robot for the user/group.
  2. Select the credential store to be used for your password. Click here for details about credential stores.
  3. Fill in the password used to log on to the machine on which UiPath Robot is installed.
  4. Select the Credential Type from the drop-down.
  5. Optional: If you opted for a CyberArk® credential store, indicate the External Name. If not specified, the default value is used.
  6. Enable the Disable Concurrent Execution option to restrict a user from simultaneously executing multiple jobs.

Robot Settings

Not available for directory groups.

📘

Note

Groups are added with the default execution settings. To customize execution settings for directory users, make the adjustments per user once they have been auto-provisioned or added manually.

  1. Configure execution settings for the corresponding UiPath Robot.
  2. Click Add. The user/group is created and displayed on the Users page. According to the Attended Robot and Unattended Robot tabs, one floating robot is created for each user.

Adding Local Users


On the Users page, click the Add button, and select Add Local User. The Add Local User window is displayed.

User Details

  1. In the Username field, fill in a username for the user.
  2. In the Name, Surname, Email fields, enter the corresponding user details.
  3. In the Password and Confirm Password fields, enter the password with which this user logs in to Orchestrator.
    The password must be at least 8 characters long and contain at least one lowercase letter and one number.
  4. From the Roles drop-down, select the roles for this user.
  5. Under UI Profile, select the user interface profile for this user/group. Only applicable if personal workspaces are enabled.
  6. Use the Allow Web Login toggle to select if this user can log in to Orchestrator.

Use the Allow Basic Authentication toggle to select if this user can authenticate to Orchestrator using basic authentication. This toggle is only available if the RestrictBasicAuthentication app setting in appsetting.Production.json is set to true.

Attended Robot

  1. Use the toggle to select whether or not to automatically create an attended robot for this user.
  2. In the Domain\Username field, fill in the domain and username of the corresponding user. For local Windows accounts use the host_machine_name\username syntax.
  3. Select the License Type for the robot to be created. Learn about license types.
  4. For licenses that grant Studio/StudioX/StudioPro capabilities (Citizen Developer, RPA Developer, RPA Developer Pro respectively), select the Stand-alone license checkbox if the Studios are licensed locally such that Orchestrator doesn't allocate a license from its pool of licenses.
  5. Select the Automatically create a Personal Workspace for this user checkbox to enable personal workspace creation for that user.

Unattended Robot

  1. Use the toggle to select whether or not to automatically create an unattended robot for this user.
  2. In the Domain\Usernamefield, identify the user associated with the robot:
    • For domain-joined users, use the domain\username syntax. For example deskover\localUser1.
    • For local Windows accounts, use the host_machine_name\username syntax, with the host machine's name instead of the domain. For example, LAPTOP1935\localUser2.
    • For local Windows accounts residing on multiple host machines, which you want to use regardless of machine, use the .\username syntax with a dot instead of the host machine name. For example .\localUser3.
  3. Select the credential store to be used for your password. Click here for details about credential stores.
  4. Fill in the password used to log on to the machine on which UiPath Robot is installed.
  5. Select the Credential Type from the drop-down.
  6. Optional: If you opted for a CyberArk® credential store, indicate the External Name. If not specified, the default value is used.
  7. Enable the Disable Concurrent Execution option to restrict a user from simultaneously executing multiple jobs.

Robot Settings

  1. Configure execution settings for the corresponding UiPath Robot.
  2. Click Add. The user/group is created and displayed on the Users page. According to the Attended Robot and Unattended Robot tabs, one floating robot is created for each user.

Editing a User


  1. On the Users page, click the More Actions button corresponding to the desired user entity.
  2. Click Edit.
  3. Make the adjustments and click Save.

Checking User Permissions


To check the permissions of a user entity, do the following:

  1. On the Users page, click the More Actions button corresponding to the desired user entity.
  2. Click Check Permissions.
  3. The User Permissions window is displayed. Each permission is listed on a per-folder basis. Adjacent to each permission, you can see whether it has been explicitly assigned or inherited from the tenant.

Removing a User/Group


  1. On the Users page, click the More Actions button corresponding to the desired user/group.
  2. Click Remove and confirm the operation on the confirmation window displayed. The user/group is deleted.

Alternatively, select one or multiple users, and click the Remove button.

🚧

Important!

  • You cannot delete a user having the Administrator role.

  • Removing a directory group does not remove the license of an associated directory user, even if the group removal unassigns the user from any folder. The only way to release the license is to close the Assistant.

🚧

Important!

Users part of mappings that are employed in triggers cannot be deleted or unassigned from the folder the trigger resides in. Make sure the user is not set as an execution target in a trigger so you can delete them.

Updated 2 months ago


Managing Users


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.