What exactly happens when you connect an Assistant?

Help Studio
1

I’m really trying to understand what happens at installation of Studio & Assistant in regards to Robot and User privileges.

Specifically, I notice that a new Robot appears under Tenant. This Robot is of type “Local User” and “Attended”.

gijoe_userrobot
gijoe_userrobot2242×583 67.5 KB

But, under Admin > Robot Accounts, it isn’t there.

image
image1629×708 50.1 KB

So my question is, what exactly has happened when one connects to Assistant? Is the current User given Robot privileges directly? Or did that user already have those permissions via its Role of Automation Developer? Is that why it suddenly appears as a Robot under Tenant?

Question 2: What exactly is the permission required to RUN an automation? Is it Job → View? or is it something else?

Question 3: Does that mean that any account or role that has permissions to run automations will automatically appear under Tenant > Robots? Or does something else have to happen?

In other words, I’m trying to figure out what UiPath did under the hood to make the User capable of running Attended automations, and why it appears under Tenant > Robots.

I also notice that at this stage our User is only allowed to run Attended automations. I understand that to run Unattended, a license must be added. Is a license added to a User, the machine, or both? Can an Unattended license be added to a Group or Role that the user belongs to? How is that done?

I’ve read all the docs on this, but am still confused by it all. Can someone explain this to me clearly?

2

@Terry_Marr

  1. When you sign in from assistant depending on the user you sign in the roles are given for the user to make it an attended robot by giving the robot role to the users which makes it a robot
  2. It is added under tenant as that user robot is created for that tenant specifically and not across thw tenants as the permissions are given at the tenant level by default
  3. The licenses are assigned to machines for unattended and testing scenarios
  4. Roles are assigned to users
  5. Based on the license type we choose it is tagged to either users or across users. For example named user license is tagged to a user account and can be assigned only to that user on the other hand flex license is not tagged to a user and can be juggled
  6. The permissions and role assignement can be done at user level or user group level as well

Hope this helps

Cheers

3

So tell me if I got this right:

  1. The permission a User or a Robot Account, or one of their Roles, needs to be able to RUN a job is Jobs → View
  2. To be able to run an Unattended Automation, the User or Robot Account, or one of their Roles, must have Jobs > View permission AND the machine must also have a license and log in credentials attached?

Is that right?

4

@Terry_Marr

  1. To run jobs view would not be enough…robot is a role that is needed you can check the minimum permissions needed are those associated with robot role…go to tenat → roles to check those
  2. As far as unattended is concerned machine needs a license too along with the user robot roles

cheers

5

I still don’t understand how the User suddenly appeared under Robots section of the Tenant. What EXACTLY happened to put him here?

gijoe_userrobot
gijoe_userrobot2242×583 67.5 KB

What qualifies a User as a Robot in order to pop up here?

6

@Terry_Marr

Go to manage access and edit the user you would see a robot tole that is what wualifies it to be under robots

Cheers

7

Ok, I tried adding the Robot Role to another user and they did not pop up as a Robot under tenant. What exactly makes them pop up there as Attended User?