Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

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

Tenant and Folder Resources


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

Tenant Resources

Folder Resources

Robots
Folders
Manage Access
Machines
Packages
Libraries
ML Skills
ML Logs
Audit
Credential Stores
Webhooks
Licenses
Alerts

Subfolders
Processes
Jobs
Execution Media
Triggers
Logs
Monitoring
Queues
Transactions
Assets
Storage Buckets
Storage Files
Folder Packages
Actions
Test Case Execution Artifacts
Test Data Queue Items
Test Data Queues
Test Set Executions
Test Sets
Test Set Schedules

These entities can be included in multiple folders of a hierarchical structure or be specific to each 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.

Folders with a dedicated package feed are marked with a Folder Packages label below the Folder name.

Folder Access


To manage the access an account has in a folder, assign one or several Folder roles that include the necessary Folder Permissions for each of the folder-level resources listed in Tenant and Folder Resources.
Although some roles are Mixed roles by default, you can only use permissions of a single type - Tenant or Folder permissions - in any role custom roles you create.

Depending on the access level you wish to grant, a combination of multiple roles is often required. Learn more about Orchestrator's access control model in About Managing User Access.

Subfolder Access

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 to which you are assigned.

🚧

Important!

Performance degradation and possible errors occur when loading the Folder selection menu for an account assigned to more than 1,000 folders.

Working Across Folders


Using modern folders, your automation workflow, executed from one folder, can access resources in another folder using the Orchestrator Folder Path parameter of the Orchestrator activities such as Get Asset.

Relative folder paths are supported in the Orchestrator Folder Path parameter, as follows:

  • Path starting with / - starts from the root folder of the tree the ambient folder is part of.
  • Path starting with . - starts from the ambient folder.
  • Path starting with .. - starts one level up in the hierarchy of the ambient folder for each .. in the path (e.g. ../ for one level up, ../../ for two levels up in the hierarchy).
    Note: Going beyond the root folder takes you to the root folder if the folder name you are trying to reach is the root name, otherwise, it fails. For example, if your root folder is called Finance and is 2 levels above the ambient folder then the ../../../Finance path works, but the ../../../Accounting path fails.

Note that trailing slashes are not accepted.

Folder Permissions


Two permission sets dictate the account abilities concerning folders: Folders and Subfolders.

Folders Permission

Subfolders Permission

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

Create / Edit / Delete Subfolders
Assign accounts to folders

The Folder Packages permission set controls access to folder packages.

Updated 2 days ago


Folders


Suggested Edits are limited on API Reference Pages

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