How to Configure a 'Read-Only' Role in UiPath Orchestrator to Prevent Users from Running Processes
Issue Description
The user created a custom 'read-only' role with just view permissions in Orchestrator.
However, when this role is linked to a directory group, the members of this group are observed to have the capability to run processes via UiPath Assistant. The context of view permissions was believed to prohibit users from executing processes from UiPath Assistant. The query was raised regarding the effect of leaving all permissions blank on forming a 'read-only' role.
Resolution
To configure a 'read-only' user role without permission to run processes from UiPath Assistant, follow the steps below:
- Access the UiPath Orchestrator and navigate to the 'Roles' section.
- Verify the permissions assigned to the custom 'read-only' role. Ensure that only view permissions are selected and no execute permissions are granted.
- Check that no licenses are allocated to users with the 'read-only' role. This prevents them from running processes.
- Navigate to the 'Licenses' section in Orchestrator and check the license allocation for the users in the directory group.
- Refer to the UiPath documentation for managing roles and permissions to understand the expected behavior and configuration: Orchestrator - Managing Roles
- Leaving all permissions blanks will not act as a true 'read-only' role. Users will lack permissions to view anything, including processes and assets. Make sure that view permissions are correctly configured to allow visibility without execution rights.