Difference between the rules Allow To Be Automation Developer and Automation Developer

Help Orchestrator
1

I didn’t understand the difference between the rules even looking at the permissions of each one.
But in practice what would be the difference between them? If I had to allocate a user to one of two rules, what should I evaluate to make the best choice?

Thanks!

2

UiPath Orchestrator uses roles to control user access.

Global Roles: Apply to the entire Orchestrator tenant.
Folder-Level Roles: Restrict access to specific folders.

Key Considerations:

1 Scope of Access: Global vs. Folder-level
2 Permissions: Read-Only, Read-Write, Execute
3 User Responsibilities: What tasks will they perform?
4 Required Access Level: What level of access is needed?
5 Security: Minimize risks by assigning appropriate roles.

you can ensure users have the necessary access while maintaining security within your Orchestrator environment.

You can explore all these key factors by publishing your own projects
Hope this finds you well !

3

In UiPath - Role is mainly classified into 2 - Tenant Role and Folder Role

image
image370×241 10.6 KB

So for any role, let’s say - Automation Developer. It needs to be defined at folder level and Tenant level. As a practice - Any role defined at a folder is started with the keyword Allow to be . Tenant role will be just the role name without Allow to be.

To answer your question - If you want to assign someone Automation Developer - You have to select both. Allow to be Automation Developer which will give access at a folder level and Automation Developer which will allow access at a tenant level

Same applicable for all other roles.

image
image604×499 31.4 KB

Very few roles are global for which you need to give only one role. Example - Administrator role

Hope this helps @rpa_dev_1

1 Like