# Folders > 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. 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. Please note, in Studio, the folder feed might not show up immediately. It is necessary to refresh the Orchestrator connection to display it. Figure 1. Folder packages ![Screenshot of the Folder packages interface](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-folder-packages-interface-226563-00d67718.webp) ## 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](https://docs.uipath.com/orchestrator/standalone/2023.10/user-guide/folders#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 custom roles you create. Depending on the access level you wish to grant, a combination of multiple roles is often required. ### Subfolder access A folder hierarchy can be established with up to 7 levels. This structure includes the top-level folder and allows for 6 additional layers of subfolders beneath it. In terms of user access, it is inherited from the parent folders. This means if you are assigned access to a folder, you automatically gain access to all of its subfolders. :::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 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](https://docs.uipath.com/activities/docs/get-robot-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). 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 Operations within folders are governed by two primary permission sets: * **Folder Permissions**: These permissions apply to the main or root folders of the hierarchy. They grant control over who can create, edit, or delete these folders. * **Subfolder Permissions**: These permissions apply to child folders, or subfolders. They grant control over who can create, edit, or delete subfolders. There is a further permission set related to packages in folders, namely **Folder Packages**. This permission set doesn't control the folders themselves but governs the access to the packages within the folders.