> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-mp-guide/publishing/manage-published-resources/manage-published-applications.md).

# Manage published applications

When publishing an application using a wizard, you specify multiple application parameters such as name, executable path, etc. You can modify these options after the application has been published.

To modify a published application, select it in the **Publishing** pane and then click **Edit** in the right pane to enable editing. Modify the application properties as described below.

Note that most of the settings here are the same as the settings in the application publishing wizard. For details about individual settings, please also see [**Publish an application**.](/landing/ras-mp-guide/publishing/publish-an-application.md) The descriptions below focus on settings that are not available in the wizard and can only be set here.

## **Application**

Most of the settings in this view are the same as in the publishing wizard. The new set of options is **Per server settings**. If the application is published from multiple servers, you can set the following application properties individually for each server:

* **Target**
* **Start in**
* **Parameters**

As an example, you can change the above properties when different servers have the application installed in different folders, so that the **Target** and **Start in** field values are valid on each server.

## **Filtering**

The options in the **Filtering** category are not available in the publishing wizard and can only be set here. The category is common for published resources of all types. For complete details, see [**Using filtering rules**](/landing/ras-mp-guide/publishing/manage-published-resources/using-filtering-rules.md).

## **Routing**

Please see [**Configuring preferred routing**](https://download.parallels.com/ras/v19/docs/en_US/Parallels-RAS-19-Management-Portal-Guide/47950.htm).

## **Shortcuts**

This view allows you to configure where a shortcut for the application is created on a user device. These settings are inherited from site defaults, but can be customized for a given application. For details, please see [**Site defaults (Publishing)**](/landing/ras-mp-guide/publishing/manage-published-resources/site-defaults-publishing.md).

## **File extension**

This category allows you to modify file extension association for the application. To add, remove, or modify an entry, select the **Associate File Extensions** option. To add a new extension to the list, choose **Add** from the ellipsis menu and specify the desired extension. To modify an existing association, select the extension in the list and choose **Properties** from the ellipsis menu.

## **License**

See [**Site defaults (Publishing)**](/landing/ras-mp-guide/publishing/manage-published-resources/site-defaults-publishing.md).

## **Display**

See [**Site defaults (Publishing)**](/landing/ras-mp-guide/publishing/manage-published-resources/site-defaults-publishing.md)**.**

If you made changes, click the **Save** button or click **Cancel** to discard them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/ras-mp-guide/publishing/manage-published-resources/manage-published-applications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.