UiPath Orchestrator

The UiPath Orchestrator Guide

A folder is a storage area that helps keep your projects separate as they enable you to maintain fine-grained control over automations and their intrinsic entities, and personnel across the entire organization.

Folders have their own Orchestrator resources that reside within each specific folder. There are also global resources that are created at the tenant level and are available across folders.

These entities can be included in multiple folders of a hierarchical structure, or be specific to each individual folder or subfolder. Only those available in the active folder are visible in Orchestrator. Switching the active folder will also update the entities, and their contents, visible in Orchestrator.

Folder Packages

Root folders can be configured with a dedicated package feed, in which case packages are a folder-specific resource, meaning they are kept separate and only available in the folder they have been published to.

Access to the packages is controlled by the Folder Packages permission.
Folders with a dedicated package feed are marked with a Folder Packages label below the Folder name.

Folder Access

To manage user access in this organizational structure, for each of the above categories there is a dedicated permissions section that controls it, Tenant Permissions and Folder Permissions. It is recommended to only use permissions of a single type in a single role. Depending on the access level you wish to grant, a combination of the two is often required.
Learn more about Orchestrator's access control model on the About Roles page.

Folders support a hierarchical structure where you can have up to six subfolders under each first-level folder. User access is inherited from parent folders such that you have access to any subfolder(s) of a folder you are assigned to.


Folders alongside Robot auto-provisioning and AD integration set the stage for effortless large deployments. See here how to manage such a deployment in Orchestrator.
The user and the automatically provisioned robot are linked, with the robot available for process execution in any folder where the user has access.



Performance degradation and possible errors occur when loading the Folder Selection menu for a user assigned to more than 1,000 folders.

Folder Permissions

There are two permission sets that dictate the users' abilities with respect to folders: Folders and Subfolders.

Folders Permission

Subfolders Permission

Create / Edit / Delete First Level Folders
Assign users to folders

Create / Edit / Delete Subfolders
Assign users to folders

Updated about a month ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.