# Deploy a release

> :::note
In this guide, it is assumed there is only one environment.
:::

## Introduction

:::note
In this guide, it is assumed there is only one environment.
:::

Deploying a release requires the following steps:

1. If the release is not available on the server where it is being deployed, it must be acquired first. This can be done by either importing a release from a repository, or by uploading it.

Furthermore, the build that the release uses should also be made available on the server if it is not already.
2. The release is activated. If the release is activated for the first time, default user access rights should be configured.
3. If the release is being deployed for the first time, user access rights will need to be configured.

## Uploading a release

A release that has been made available by a developer as an `.mvtag` file can be uploaded to the server either by using the upload option, or by dragging a release file onto the **Superadmin Releases** tab.

Follow these steps to upload a release.

| Step | Action |
| --- | --- |
| 1 | Go to the **Superadmin Releases** tab. |
| 2 | Click on the menu icon in the top-left and select **Upload a release to this server…**. |
| 3 | Drag the desired release file onto the **Upload File** dialog or browse for it on your computer. |
| 4 | Click on **OK**. |

:::note
You can also drag the desired release file to the **Releases** tab.
:::

The uploaded release is now visible in the list of releases.

## Importing a release

An existing release can be imported from a repository.

Follow these steps to import a release from the repository.

| Step | Action |
| --- | --- |
| 1 | Go to the **Superadmin Releases** tab. |
| 2 | Click on the menu icon in the top-left and select **Import a release from the repository…**. |
| 3 | Select the repository that contains the desired release. |
| 4 | Select the branch that contains the desired release. |
| 5 | Select the desired release. |
| 6 | Click on **IMPORT**. |

The imported release is now visible in the list of releases.

## Uploading a build

The build used by the release must be available on the server to be able to activate the release. Which build is used by the release can be seen in the **Build** column in the **Releases** tab. If it is not yet available, the required build can be uploaded in the **Builds** tab. The build should be made available by the developer.

Follow these steps to upload a build.

| Step | Action |
| --- | --- |
| 1 | Go to the **Superadmin Builds** tab. |
| 2 | Click on the menu icon in the top-left and select **Upload build…**. |
| 3 | Drag the desired build file onto the dialog or browse for it on your computer and click on **OK**. |
| 4 | Right click in the list on the build that has been uploaded and select **Activate as Superadmin**. |

:::note
You can also drag the desired build file to the **Builds** tab.
:::

The uploaded build is now activated and visible in the list of builds.

See: [The Builds Tab](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/the-builds-tab#the-builds-tab).

## Activating releases

When activating a release, a dialog is shown. Any modules not present in the previous active release are highlighted in green.

The default access rights of these new modules can be set to:

* All users: all current and future users will automatically have access to the module.
* No users: no current or future users will initially have access to the module. The individual user rights will need to be set for the module.

Any changes in the name and/or description of previously active modules will be highlighted in orange.

See illustration below.

  ![docs image](https://dev-assets.cms.uipath.com/assets/images/process-mining/process-mining-docs-image-53467-2680e0b4-2513e639.webp)

Follow these steps to activate a release.

| Step | Action |
| --- | --- |
| 1 | Go to the **Superadmin Releases** tab. |
| 2 | Right click on the release that is to be activated. |
| 3 | Select **Make active on - production**. |
| 4 | Select the desired default access for new modules, if any. |
| 5 | Click **OK**. |

The **Active on** column now says production in front of the activated release and the release can be accessed by users with the proper access rights once a cache has been generated.

See: [The Releases Tab](https://docs.uipath.com/process-mining/standalone/2021.10/user-guide/the-releases-tab#the-releases-tab).

### Automated release deployment

The following command-line functions are available that you can use to automate your release pipeline:

* `ImportRelease` to import releases either from a local file or a Git repository.
* `ActivateRelease` to activate the release.

You can use these commands in a batch script, to automatically release a new version to different (production) environments. For example, the `processgold.bat` script that is available in the **Builds** folder of your **UiPath Process Mining** installation.