What Orchestrator for Citizen Developers / Folder organization

Help Orchestrator
1

Hello

  • What specific roles would you grant to Citizen Developers on orchestrator that just need to run attended automations or share them?

  • Also should all automations to be Shared fall in the “Shared” folder, or is it recommended to have a specific folder for attended automations?
    I cannot see the Shared folder on my assistant

2

Hi @adext01

**Roles to grant **

  • Automation User
  • Robot (Attended)**
  • Folder access (View + Run jobs)
  • Package View**
  • Package Create/Upload (only if they need to share automations)

No admin roles needed.

  • “Shared” folder is optional, not mandatory.
  • Best practice: create a dedicated folder for Attended automations and share it with users.
  • If you can’t see it in Assistant, you don’t have access to that folder (no folder role assigned).

Regards
Gokul

3

hi @adext01

For Citizen Developers (Attended only):

TENANT ROLE: "Viewer" 
FOLDER ROLE: "Automation User"

Folder Setup:

1. Create "Attended" folder (NOT Shared folder)
2. Assign "Automation User" to this folder
3. Publish attended automations here

Why “Shared” folder not visible in Assistant:

  • Shared = Unattended automations only
  • Assistant shows Attended folders only

Exact Steps:

Tenant > Manage Access > Assign "Viewer"
Attended Folder > Permissions > Assign "Automation User" 
Publish → Assistant shows it immediately

Result: Users can run + share attended automations. Zero admin access needed.

4

For Citizen Developers who only need to run attended automations or share them, permissions should be kept minimal. At the folder level, assign the Attended User role so they can view and run processes from UiPath Assistant. If they also need to publish or share automations, grant the Automation User role at the tenant level. Avoid higher-privilege roles such as Automation Developer, Folder Admin, or System Admin, as they are unnecessary and weaken governance.

From a folder-design perspective, attended automations should not be placed in the “Shared” folder. The Shared folder is intended for reusable components or libraries, not for executions. Best practice is to maintain a dedicated folder for Attended Automations, which keeps responsibilities clear and ensures correct access and visibility.

Not seeing the Shared folder in UiPath Assistant is expected. UiPath Assistant only displays attended processes from folders where the user has appropriate permissions. Since Shared folders typically do not contain attended processes, they are intentionally hidden from the Assistant.

5

Hi @adext01

Citizen Developers should be given minimal tenant access like attended user and a folder role that allows running jobs and sharing automations.

Shared automations do not have to be only in the shared folder; it’s recommended to create a dedicated folder for attended automations and share it with the required users.

The shared folder is only visible in UiPath Assistant if automations are explicitly shared and the user has the necessary folder permissions.

If helpful, mark as solution. Happy automation with UiPath

6

Hi @adext01

For Citizen Developers:

  • Tenant role: Tenant User
  • Folder role: Automation User (or custom role with run/view permissions)
  • Add Package Publisher only if they need to publish/share automations

Folder:

  • Better to use a dedicated folder for attended automations.
  • Shared folder is mainly for assets/libraries and may not appear in Assistant.
  • Assistant shows only attended processes from folders the user/machine is assigned to.