How to Configure Attended Concurrent Robot

Hi All, My issue is exatly similar with this link, but it seems no solution yet.

According to the UiPath official website, attended concurrent means that licensed only consumed when robot tray is opened regardless of the username and machine

So Asuming that I only have 1 attended concurrent license, then I install Robot Tray on 2 Different Machine (with 2 different username), It should be possible right ? As long as only 1 robot tray opened in either machine then the license is consumed.

However, when creating robot in orchestrator, we need to specify the domain\username and the license is automatically consumed.

Please advice

Thank you

I have not tried Concurrent licenses for Attended or Unattended Runtimes yet, so my advice is based on the documentation.

One piece that jumps out of me is


If a license file contains licenses for all types of Robots, the Concurrent ones are now prioritized over the named user ones. For example, if a license file contains both Attended Concurrent and Attended licenses, the Attended Concurrent ones are shown as available in Orchestrator.

Are you using Community Cloud? Based on the labeling Community only provides 2 Named User Licenses, if you are using Enterprise Cloud or Server, do you see options to adjust your concurrent licensing? Assuming you’ve already purchased an concurrent/multiuser license.

@Forum_Staff - Any chance we could get clarification on this? How does the concurrent licensing for the different Robot Types behave? Once a license with concurrent/multiuser is activated, is there a difference in the UI to show this?

Current Commercial Licensing
Some user types offer the option of a Multiuser license model1 as described in the table below. The Multiuser license option is available solely with the purchase of the Multiuser add-on available for Orchestrator Standard.

1 Multiuser license types are displayed in the Orchestrator as Concurrent User

2018.4 / 2019.4 / 2019-10
Any User can access ST in an active Desktop session. ST may be licensed on multiple Machines and is activated via OC using a Development License. One ST license may not be active on more than one active Desktop session at any given point in time. The Customer must obtain separate licenses for each User simultaneously accessing ST.

1 Like

I have not purchased concurrent license yet, as my vendor said concurrent license will be discontinued soon. Therefore, I am assuming that the alternatives, they changed it into multiuser license model.

However, this raise more questions for me, according the website

All user types are available under a Named User license model.
The Multiuser license option is available solely with the purchase of the Multiuser add-on available for Orchestrator Standard.

So there are 3 deductions here
a. All User now are named user by default
b. Multiuser is additional add-on (does it mean we need to repurchase again ? )
c. Multiuser is only available for orchestrator standard (not in the cloud platform?)

Yes I Agree, Hopefully someone from uipath official will give some clarification on this, how to set it up, or any UI differences

If you buy 5 Multiuser Studio licenses and upload it to your Orchestrator then

  • you can define 15 users with Studio
  • only 5 can work simultaneously

With concurrent you would have had the possibility to define unlimited users.


Taken from the Licensing Guide

Multiuser License
UiPath is transitioning from Concurrent user license to Named User in alignment with the enterprise software market standard. This alleviates the challenges where only one user per license can be logged in at any time resulting in license not always available when needed. With Named user, every user has a dedicated license and always there when needed.

Multiuser license is introduced for cases such as Call Center where there’s shift workers or variable staff across multiple time zones, part-time staff, or seasonally augmented staff. Multiuser is only available on Orchestrator Standard. The Admin defines a list of authorized named users which can claim a license. Licenses are allocated on a first come, first server basis up to the cap of the concurrent licenses purchased. 1 (one) Multiuser license allows up to 3 (three) authorized users (1 at a time). 100 Multiuser licenses will allow up to 300 authorized users defined.

In addition to the above changes, Node Locked will not be available for Studio and Attended Robot. Node Locked will transition to Named User or Orchestrated Multiuser to benefit from the full capabilities of the services for scale. There will be options to upgrade products to the orchestrator and multiuser license will enable support for multiple users on the same license. This enables the ability to use the same license for the same user on different machines

I’m assuming what is meant by standard is their Enterprise offering. They have Community Cloud, Enterprise Cloud, & Enterprise Server.

@badita - Could you confirm that it is an alternate licensing purchase opposed to, in addition to the standard license?

If you have more question, I’d suggest reaching out directly to their sales or Cloud support team.


Hi everyone!

The Attended Robot has a per user license with 2 license models: Named User and Multiuser (former Concurrent User).

In your example, it means that 2 different users may execute processes but one at a time (only 1 simultaneously).

Since Attended has a per user license, specifying the domain\username is mandatory so that Orchestrator will know if you have the same user or different ones.

How it works in your case: you go to Robots page and provision two different users of type Attended Concurrent. When you connect the robot on User1 to Orchestrator, the license is consumed (because we said above that maximum 1 user can be connected in this case). Then you try to connect the second one (User2) and it should say that it’s unlincensed. In order to free a license, User1 will have to Quit the Robot tray. Then User2 will pick up that slot.

The changes regarding Concurrent and Multiuser are the ones stated by badita above: with Concurrent you can provision unlimited users (provision = define in Orchestrator) and with Multiuser a limitation was added - you can define in Orch maximum 3 x No. of Multiuser licenses purchased.

a. Yes
b. Yes, commercially, you need the Multiuser add-on. You have to purchase the Multiuser add-on at the same time as you purchase or renew onto Multiuser licenses.
c. Yes, Multiuser is only for Orchestrator Standard. And it can also be used in Cloud (you can see in - Cloud Orchestrated Attended - Multiuser but since in Cloud Platform you don’t buy the Orchestrator, only the Robots, it’s not specified). What does this mean? Commercially, there are two types of Orchestrator:

  • Basic - 1 tenant allowed to use in Production and maximum 5 robots of each (Attended/Unattended/Studio). This is intended for small deployments, customers who just start their automation journey.
  • Standard - no limits for tenants or number of robots. This is intended for medium and large deployments, where customers have to manage dozens/hundreds of robots and processes (and other resources).
    Multiuser license is introduced for cases such as Call Center where there’s shift workers or variable staff across multiple time zones, part-time staff, or seasonally augmented staff. Since Multiuser is also intended for a large amount of possible users, it can only be used with an Orchestrator Standard.

Community and Enterprise are Subscriptions of the products.
Orchestrator Basic and Standard are commercial offerings of the Enterprise subscription.
Cloud and On-premise/Server are deployment types.


@Stephu regarding your question here: Disconnect attended robot after job or change the attendent licence model. Check if the above answers help.

thanks !

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.