How can unattened user be given a dev license?

Help Orchestrator
, , ,
1

Hello All,
We have 7 automation developer named user licenses.
Out of this, 5 are always in use by dev team and they are tagged to their user accounts.
There are 2 free licenses which are required sometimes to be assigned to prod accounts so we can test using prod data.
Is there a way to allocate this license to a group (like Automation Developers) so that anyone who is connecting from the group would get the license and will be able to open studio with the dev license. We also have some temporary developers who do not work at the same time.

Scenario is there are 10+ different users accounts in prod and I want developers to be able to use these accounts to login to studio for testing from their machines. Also for some additional developers.
So I want a provision to get the 2 licenses available to around 15 user accounts using a group or whatever is required.

I understand it is possible to set up troubleshooting sessions from orchestrator, but that is in prod VM, which is not the goal

2

@SnehajitDas

As it is named user license…i dont think you can tag it to a pool of users

The image explains the policy and conditions of Named User licenses for UiPath software, noting that Multiuser or Concurrent User licenses are discontinued and providing a link for more information. (Captioned by AI)
The image explains the policy and conditions of Named User licenses for UiPath software, noting that Multiuser or Concurrent User licenses are discontinued and providing a link for more information. (Captioned by AI)828×980 148 KB

Cheers

3

There are no other type of dev license than named user.
So can we conclude that it is not at all possible to have a pool of users with limited number of licenses which can be used by them on need basis?

4

Hi @SnehajitDas,

Developer licenses are only meant to do development and local testing from studio.

You won’t be able to use these licenses to run processes in an unattended way which is usually the goal of having unattended licenses so we can test our process in an unattended way i.e. from orchestrator without using studio.

Also, it is not advisable to have access enabled for developers on prod environment. But again, this can vary for different organizations based on their preferences/set-up.

Usually, A proper approach would be to have the segregation of environments(dev,uat,prod) so proper access rights and licenses can be enabled in the same.
DEV → developer license only intended to develop and unit testing from studio
UAT → unattended license for testing the process from orchestrator(not studio) in non-prod environment before promoting it to prod environment
PROD → unattended license for testing the process from orchestrator(not studio)

Hope this helps.

Regards
Sonali