# Packages > The **Packages** page in Orchestrator displays all the projects [published from UiPath® Studio](https://docs.uipath.com/studio/docs/about-publishing-automation-projects), and the ones that were [manually uploaded](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-packages#managing-packages). The **Packages** page in Orchestrator displays all the projects [published from UiPath® Studio](https://docs.uipath.com/studio/docs/about-publishing-automation-projects), and the ones that were [manually uploaded](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-packages#managing-packages). Internal packages, namely Orchestrator-hosted feeds packages, are sorted by published date. The published date is the date when the most recent version of a package was published. ## Package Feeds Feeds are package streams that allow you to store and group packages in order to control their availability and isolation. :::important * We do not support cross-platform packages uploaded to an external feed. Their metadata can only be read if they are uploaded directly to Orchestrator. * The package's release notes should not exceed 35000 characters. Otherwise, the content is trimmed to fit this limit. * Using v3 NuGet feed URLs results in a couple of display issues with packages. + The publish date of a package is not correct. + For MyGet feeds, the total number of packages is much greater than the actual number of packages uploaded to the feed. ::: ### Tenant feed :::note Feature availability depends on the cloud offering that you use. For details, refer to the [Feature availability page](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/orchestrator-feature-availability#orchestrator-feature-availability). ::: Packages added to the tenant feed are global resources, meaning they are available across folders. They are referred to as simply "packages" and are managed on the **Packages** page (**Tenant** context > **Packages**). For packages published or uploaded via UiPath® means, such as packages published from Studio or uploaded to an internal feed, Orchestrator automatically determines the package type and displays the packages in the corresponding grids under **Tenant** > **Packages**: * **Libraries** – this grid displays libraries. A library describes a system of activities with a well-contoured business function, making them suitable for sharing and reusability. For more information, see [About Libraries](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-libraries#about-libraries). * **Apps** – this grid includes two dedicated views: + **Apps** – web apps published from Studio Web. + **App Versions** – the available versions for each published app. For more information, check [Version Management](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-apps#version-management). :::note The **Apps** tab and the corresponding grid are visible only if you have the **App Creator** role. ::: * **Test** – this grid displays test automation packages published from Studio. * **Feed** – this grid displays the raw list of packages from the configured feed. The list includes both packages published or uploaded via UiPath® means and items manually uploaded to the feed via external tools. To ensure that you can use a package that was manually uploaded to the feed via external tools, you must import it by using one of the following options: + To import the latest version of the package, select **More actions** > **Import latest version**. + To import a previous version of the package, select **More actions** > **View versions**, then locate the relevant version in the list and select **Import version**. Packages published or uploaded via UiPath® means are always imported by default. You can configure feed settings and security from the tenant settings > **Deployment** tab, either at the tenant level or from the Orchestrator host portal. Settings here only affect tenant feeds; folder feeds and personal workspace feeds are always internal and available in the context of the respective folder or personal workspace alone. ### Folder feed Packages added to a folder feed are folder-specific resources, meaning they are kept separate and only available in the folder they have been added to. They are often referred to as "folder packages" and are managed on the **Folder Packages** page (**Folder** context > **Automations** tab > **Folder Packages**). To display only packages belonging to a certain type or selection of types, use the **Type** filter. Only root folders can be configured with a dedicated package feed. All subfolders inherit the package feed setting from the root parent. Access to the feed is controlled by the folder-scoped **Folder Packages** permission set. Please note, in Studio, the folder feed might not show up immediately. It is necessary to refresh the Orchestrator connection to display it. :::note Folder feeds can only be used for processes. They cannot be used for libraries. ::: ### Personal workspace feed A personal workspace feed resembles a folder feed. Packages published to a personal workspace feed are workspace-specific resources, meaning they are kept separate and only available in the workspace they have been added to. A personal workspace comes with a dedicated feed by default. Packages added to a workspace feed are automatically deployed as processes in the context of that workspace. They are managed on the **Folder Packages** page (**Personal Workspace** context > **Automations** tab > **Folder Packages**). ### Custom feed A custom NuGet feed or a local folder. ## Package Versions Package versioning is configured in Studio when publishing a package to Orchestrator or other custom location. For details on the available versioning schemas, check the Studio article [here](https://docs.uipath.com/studio/v2020.4/docs/about-automation-projects#section-semantic-versioning). Release notes for a package version and [input or output parameters](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-input-and-output-arguments#about-input-and-output-arguments) have to be configured in Studio to be accessible in Orchestrator. The first mentioned feature enables developers to track changes between package versions, while the latter enables you to better integrate third-party tools. A package version can have the following statuses: * **Active** - it is currently deployed to a process or a folder; * **Inactive** - it is not currently deployed to a process or a folder (only these can be deleted). ## Package Migration To help you migrate packages from one Orchestrator instance to the other with ease, such as from a testing environment to a production one, it is possible to download any version, be it active or not. Please note that this is only possible if you are using an [internal feed](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configuring-tenant-settings#packages), and you have **View** permissions on Packages. From here, you can upload one or multiple packages to another Orchestrator, by using the **Upload** button. When uploading such `.nupkg` archives manually, you can also check if there are any existing processes that can be upgraded and perform that action instantly, as described [here](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-packages#managing-packages). ## Package Explorer Similar to the Studio **Designer** panel, the **Explore Package** option enables you to view and explore the graphical representation of any `.xaml` file that is part of a package version. The file set as Main is labeled accordingly, and all dependencies are mentioned for each package version. :::note * You can only view packages in [internal feeds](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configuring-tenant-settings#packages) using the **Package Explorer**. * Make sure you select the package version within the package explorer to view its details. ::: You can view all variables, arguments, and imports created for a specific package, similar to Studio. The properties of an activity are displayed if selected, along with their values, if any. For more details, check [Managing Packages](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-packages#managing-packages). :::note Flowcharts are displayed similarly to standard workflow diagrams. ::: Figure 1. Process flowchart ![Screenshot of a process flowchart](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-a-process-flowchart-228491-79ddcbe8-e609e3ad.webp) In addition, the **Explore Package** allows you to compare the differences between any two selected versions of a package, which points out workflow files that you added, modified, or deleted, and highlights changes in folders or the dependencies list. It is possible to view the differences between the selected versions of the workflow `.xaml` files, presented side by side, earliest file version on the left, with deleted content highlighted in red, modified content in yellow, and added content in green. For more details on how to compare package versions and workflows, check [here](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-packages#managing-packages). Figure 2. Comparing flowcharts ![Screenshot of the comparing flowcharts interface](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-comparing-flowcharts-interface-233266-68bea2dc-e19f3e04.webp) ## Package Permissions To perform various actions on the **Packages** page, you need to be granted the corresponding permissions on Packages: * **View** - view all package-related details, view which processes can be upgraded, and explore and download packages (these two also require internal feeds); * **Edit** - doesn't grant any additional rights at the moment; * **Create** - manually upload packages or publish them from Studio; * **Delete** - delete inactive packages. To perform various actions on the **Folder Packages** page, you need to be granted the corresponding permissions on Folder Packages: * **View** - view all folder package-related details, view which processes can be upgraded, and explore and download folder packages (these two also require internal feeds); * **Edit** - doesn't grant any additional rights at the moment; * **Create** - manually upload folder packages or publish them from Studio; * **Delete** - delete inactive folder packages.