Hello guys. I invited a new user, who will help me check if all my automations are running well, but it seems he cant see orchestrator at all. Wanted to ask for help, how can I give him the access?
To let the user see Orchestrator jobs, you need to give access at both levels:
- Add the user to the tenant
- Automation Cloud β Admin β Manage Access
- Assign a role that includes Orchestrator access
- Grant folder permissions
- Orchestrator β Folders β Manage Access
- Assign a role with:
- Jobs β View
- (Optionally) Robots / Processes β View
Without folder-level access, Orchestrator wonβt be visible even if the user is invited.
Thanks for the reply! He can see the orchestrator now, but I noticed, that the automations are all published in my personal workspace. He wont be able to see it i believe without admin privelages. How can I set it up, so he would even see them? Should i republish my projects to a shared folder?
Youβre right. Personal Workspace automations are visible only to you.
To let others see them without admin rights, republish the projects to a Shared Folder and give the user View permissions (Jobs / Processes) on that folder.
Thanks a lot! Will try in a second and let you know
Automations published in a personal workspace are only visible to you, regardless of their role or privileges.
To make them visible:
- Create or use an existing shared folder in Orchestrator.
- Assign the new user to that folder with the right role (e.g., Robot, Viewer, or custom role depending on what you want them to do).
- Republish your projects to the shared folder so they are accessible to others.
This way, the user can see and monitor the automations without requiring admin privileges.
If helpful, mark as solution. Happy automation with UiPath! ![]()
Personal Workspace processes canβt be visible to other users.
Republish the processes to the folder where your other users have the access.
No one can see your automations published in personal workspace except you. Not even admins.
As suggested by other users in this post, kindly publish your automation in another folder and give access for that folder to the new user. Then that person will be able to access the automations.
Inviting the user alone wonβt give Orchestrator access. You need to add the user to the correct tenant and assign a role (Viewer / Automation User) at tenant or folder level. After that, ask them to log out and log in again Orchestrator should show up.