# Managing Libraries

> :::note
Uploading a library requires your user to have **Create** permissions on Libraries.
:::

## Manually Uploading a Library to Orchestrator

:::note
Uploading a library requires your user to have **Create** permissions on Libraries.
:::

This functionality is useful when, for example, the Studio instance in which you design processes is not connected to Orchestrator.

1. On the **Libraries** page, click **Upload**. The **Upload Library** window is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-232109-eb9cbcab.webp)
2. Click **Browse** and select the library package (with the .nupkg extension) you want to upload to Orchestrator. The name of the file is displayed in the **Upload Library** window.
3. Click **Upload**. The library is uploaded to Orchestrator, and it is displayed on the **Libraries** page. It is stored either in the host feed or in the tenant feed, as configured on the **Deployment** tab, in the **Settings** page.

## Downloading a Package Version for a Library

:::note
The **Download** button is enabled for libraries only if you use a local feed, and you have **View** permissions on Libraries.
:::

1. In the **Libraries** page, click **View Versions**. The **Package Versions** window is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-226751-952c5338.webp)
2. On the **Versions** tab, click **Download library** for the library package version you want to download. The package is downloaded to the default location configured in your browser, in the `.nupkg` format. From here, you can upload it to another Orchestrator instance.

## Deleting Package Versions of a Library

:::note
This action depends on the settings you have chosen at the tenant level, on the **Deployment** tab:

* **Only host feed** - libraries are uploaded to the host feed, which means that they can be deleted only from the host level.
* **Only tenant feed** and **Both host and tenant feed** - libraries are uploaded to the tenant feed or to the tenant and host feed, which means that they can be deleted from the tenant level.

.
:::

1. On the **Libraries** page, click **View Versions**. The **Package Versions** window is displayed.
2. Click the **Versions** tab. You can see all package versions of the library displayed.
3. Select a specific version or multiple and click **Remove**. The selected package versions are removed.

## Displaying Release Notes for One Package Version

1. In the **Libraries** page, click **View Versions**. The **Package Versions** window is displayed.
2. Click the **Versions** tab. You can see all package versions of the library displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-227258-775fce11.webp)
3. For the desired version, click **Show Release Notes**. The **Release Notes** window is displayed, enabling you to see the note added in Studio for the respective version.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-225845-c73a0ef9.webp)

Note that you have the option to manually download package versions from the **Release Notes** window as well. The process is similar to downloading them from the **Versions** tab.

## Displaying Release Notes for All Package Versions

1. In the **Libraries** page, click **View Versions**. The **Package Versions** window is displayed.
2. Click the **Change Log** tab. You can see all package versions of the library, and for each, the corresponding release note containing information related to what has changed in-between versions.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-231176-ac487e31.webp)

Note that you have the option to manually download package versions from the **Change Log** tab as well. The process is similar to downloading them from the **Versions** tab.