Good morning,
Does anyone know if there’s a change in permissions for starting Jobs in the Orchestrator? It looks like UiPath updated UiPath cloud in the past few days as the interface changed.
If permission is set to View and Create jobs, but not Edit, it’s just showing the grey area as if it’s not quite loaded. Tried incognito mode in case it’s cached but the issue persists.
Editing input arguments used to be allowed with View and Create, as full Edit access means the setting of the job itself can be edited. Many thanks, any info would be appreciated!
Hi @byuli , It appears that a recent UiPath Cloud/Orchestrator UI update may have changed the permissions required to view or edit Start Job input arguments.
You can try with these steps:
Verify the user has View, Create, and Edit permissions for Jobs/Processes.
Test with another role that has the same permissions.
Check UiPath Cloud release notes for recent permission-related changes.
Raise a UiPath Support ticket, as this behavior differs from the previous functionality and may require confirmation from the product team.
Hi, thank you for your reply. I tried but for me it doesn’t make the runtime arguments section appear, it just opens up the normal executing parameters like picking a machine or robot.
It doesn’t sound right to give Edit access to Jobs and Create/Edit access to Processed to be able to run a job with arguments.
I’m not too sure what Edit job is for, users with View and Create have been able to change the Execution settings, and until recently, were able to see (and edit) runtime arguments.
As for processes, they should not be able to Create or Edit Processes when starting a job, it opens up a whole lot of security issues if they can rollback to other versions or create their own processes.
I could not see anything about this in the release notes, so I raised a ticket with UiPath, hoping it’s a bug
This looks like a permissions-related change/behavior in the updated Orchestrator UI.
If the user has View and Create Jobs but does not have the required Edit permission, the input arguments/entry point section may appear as a grey loading area instead of being displayed.
As a workaround, you can verify the user’s permissions for the folder/process and temporarily provide the required Edit permission to confirm whether the arguments become visible.
If Edit permission fixes the issue, it would be worth checking the latest UiPath Cloud release notes or raising a support ticket, since previously View + Create Jobs allowed users to provide input arguments when starting a job.
Thanks for this, it was permission related change.
It started on the 19/08 for us and UiPath support just said we need to give the affected users Package > View permission at the tenant level which wasn’t required before. Jobs stayed as View and Create, and View only on Processes.
There is no documentation for this in the release notes for Orchestrator for 18th August which is when I assume the change happened.
Thanks for the clarification. That confirms the issue was related to a permissions change in the recent Orchestrator Cloud update.
The Package > View permission at the tenant level was not required previously, so this is useful information for others facing the same issue. Hopefully, UiPath will add this change to the Orchestrator release notes/documentation as well.
Thanks for sharing the workaround and the details!
