Install and connect the Desktop client

The SS&C | Blue Prism® Desktop client needs to be installed on the machines of the users running processes.

To watch the Desktop client installation, see the Blue Prism Desktop installation and configuration video

This video demonstrates the installation of an earlier version of Desktop. You can use the video as guidance, but there will be some differences in Desktop 1.1.


The Desktop client requires the following components to be installed in your Blue Prism environment prior to installation.

  • SS&C | Blue Prism Enterprise Edition version 7.2 – Your Desktop license gives you access to the Desktop-specific functionality available in Blue Prism.
  • Desktop and Enterprise licenses can be applied to the same Blue Prism database. A separate Desktop environment is not required.

  • SS&C | Blue Prism API version 7.2 – The API provides an interface for Desktop to connect with the Blue Prism database. It also provides a series of predefined capabilities that are used to interact with Blue Prism programmatically using a RESTful API.
  • The Blue Prism API needs to be installed in your Desktop environment, however, there is no recommended order in which the APIs need to be installed.

  • SS&C | Blue Prism Hub version 4.7 Hub deploys Authentication Server. Authentication Server provides a centralized, common authentication method for users across key Blue Prism components, including Desktop.
  • Blue Prism Digital Worker API version 7.1 – The Blue Prism Digital Worker API provides an interface between Desktop and the Blue Prism database, allowing Desktop to retrieve processes. This must be installed before attempting to install and configure the Desktop client.

Desktop licenses

A Desktop license will need to be applied to the Blue Prism database before a user is able to sign in and use the Desktop client.

Unlike Blue Prism Enterprise licenses, whose use is determined by the number of concurrent sessions, Desktop licenses are associated with the number of registered Desktop runtime resources.

When a user logs into the Desktop client for the first time, their machine is registered as a Desktop runtime resource and a Desktop license is associated with that machine. If another user logs onto that machine, they will share the same Desktop license.

To remove a license from a machine and make it available for another machine, the Desktop system administrator will need to retire the Desktop runtime resource, see Resource management for details. Subsequent login attempts on that machine will fail until the resource is unretired.

Minimum hardware requirements

See Blue Prism software and hardware requirements for details of the minimum requirements for the computer running the Blue Prism Desktop client.

Install the Desktop client

To install the Desktop client, download and run the Desktop installer, available from the Blue Prism Portal, and progress through the installer as shown below:


Installer screen



Desktop installation welcome screen


If required, select another language for the installer from the drop-down list. The default language is English (United States).

Click Next.


Desktop installation license agreement screen License agreement

Read the End User License Agreement and if you agree to the terms, select the check box.

Click Next.


Desktop installation destination screen Destination folder

Specify the required installation folder. The default location is C:\Program Files (x86)\Blue Prism\Blue Prism Desktop, but you can choose your own using the Change button.

Click Next.


Desktop client installtion: Remote connection configuration

Remote connection configuration

Desktop users can connect to Desktop environments using one or both of the following options:

  • Shared connection file – Specify the location and name of the shared connection file. If you enter an invalid location and file name, a warning will display. If you leave the field blank, a shared connection file will not be configured.
  • Local connection files – Select Allow local connections to be configured to enable configuration of Desktop client connections using the Desktop client.

For details on Desktop connection files, see Configure a Desktop client connection.

It is strongly recommended that Desktop client connections are configured by a Blue Prism system administrator.


Advanced install

Select the additional components you would like to install. All available options are selected by default.

  • Outlook automation – Required on devices where the Blue Prism MS Outlook Email VBO will be executed.
  • Google Sheets automation – Required on devices where the Blue Prism Google Sheets VBO will be executed.
  • Chrome browser extension – Required to enable Blue Prism to interact with Chrome-based applications and web pages.
  • Edge browser extension – Required to enable Blue Prism to interact with Edge-based applications and web pages.

Click Install to install Desktop. A progress bar displays during the installation of the application.



Desktop installation installation complete screen

Installation complete

If the installation has completed successfully, click Finish to exit the installer.

If the installation fails, click View Log to see details of the error that was encountered.

Configure a Desktop client connection

It is strongly recommended that Desktopclient connections are configured by a Blue Prism system administrator.

When installing the Desktop client, users can choose to connect to the Desktop environment using at least one or both of the following options:

Configure a shared connection

If your organization wants Desktop client users to connect to a Desktop environment using a shared connection file, the location of the shared file will need to be entered when installing the Desktop client. The creation and configuration of the shared connection file should be carried out by a system administrator. Desktop client users cannot edit or delete shared connections. See Configuring environment connections for Blue Prism Desktop for details.

Desktop.User.config backup file

When a Desktop user has successfully connected to a Desktop environment using a shared connection file, a .desktop.shared.config.bak file is automatically generated and stored locally in C:\Users\<user name>\AppData\Roaming\Blue Prism Limited\Desktop. This connection file is then used to establish a connection with the Desktop environment, removing the need to connect to the shared file each time the user accesses Desktop.

Configure a local connection

Details of how users can import and connect to existing Desktop connections can be found in Configuring environment connections for Blue Prism Desktop.

The Desktop.User.config file, which is located in C:\Users\<user name>\AppData\Roaming\Blue Prism Limited\Desktop on each computer, points to the location of the Blue Prism API, the Digital Worker API, and Authentication Sever. This file can be edited directly if necessary, or configured via the Desktop user interface (recommended), as described below.

  1. Open the Desktop application.

    The Welcome to Desktop screen displays.

    Desktop Welcome > Connection screen

  2. Click Configure connection. On the Welcome screen, click Configure connection. On the Settings screen, click Saved connections. The available connections and options can vary depending on your installation of Desktop.

    The Saved connections screen displays.

    Saved connections screen

    The available connections and options on this screen are dependent on each user's installation of the Desktop client.

  3. Click Add connection. On the Saved connections screen, click Add connection.

    The Create new connection screen displays:

    Create new connection screen

  4. Enter the connection details, as prompted. All the fields are mandatory.

    Field name Information required
    Connection name

    Enter a name for this connection. Connection names must be unique, and are case‑sensitive.

    If you try to create a new connection with the same name as an existing one, a warning message displays and you cannot save the connection.

    URL for Authentication Server

    Enter the Authentication Server URL.

    To ensure a secure connection is used, all Authentication Server URLs must include https://. If you do not include https:// in the URL, it will be added automatically.

    URL for Digital Worker API Enter the URL of the Digital Worker API to which you want to connect.
    URL for Blue Prism API

    Enter the URL of the Blue Prism API to which you want to connect.

  5. Click Create to add the new connection.

    The connection is created and displays on the Saved connections screen.

    Saved connections screen Saved connections screen

The configuration is updated in the Desktop.User.config file, which is located in C:\Users\<user name>\AppData\Roaming\Blue Prism Limited\Desktop. The configuration file can then be imported by clicking Import connection on the Saved connections screen on each Desktop user’s computer. See Configure Blue Prism Desktop connections for details.

Although the functionality is available to do so, it is not expected that Desktop users will create, edit, or delete their own connections. It is expected that this information will be provided to them by system administrators. However, because the connection configuration information is stored in their user settings, they will need to import the configuration file themselves. When rolling out Desktop to end users, it is recommended that system administrators create and distribute a centrally-controlled Desktop.User.config file to be imported by Desktop users.

Example Desktop.User.config file

The following example shows a typical Desktop.User.config file:

  "Environments": {
    "Production Environment": {
      "ConfigurationName": "Production Environment",
      "ApiUrl": "",
      "DigitalWorkerApiUrl": "",
      "AuthenticationServerDomain": "",
      "ClientName": "bpd"
    "ABC connect": {
      "ConfigurationName": "ABC connect",
      "ApiUrl": "",
      "DigitalWorkerApiUrl": "",
      "AuthenticationServerDomain": "",
      "ClientName": "bpd"
  "Selected": "edadev2"