> 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/daas-guides/daas-administrators-guide/getting-started/publishing-resources.md).

# Publishing resources

Desktops based on the Golden Image and all applications installed on it can be made available to users in the **Applications** category. This is called publishing resources.

{% hint style="info" %}
**Note**: By default, Parallels DaaS deploys D2 v5 instances (2 vCPU, 8 GB memory). Please contact us if you require a different configuration.
{% endhint %}

To publish an application:

1. If you want to publish an application, make sure that it is installed on the Golden image. Desktops are always available for publishing.
2. Navigate to the **Applications** category. You will see the lists of available resources.
3. Toggle on the switch next to the resource you want to publish.

{% hint style="info" %}
**Note**: If you cannot find your application in the list of available applications, make sure the shortcut to your application exists in the `C:\Documents and Settings\All Users\Start Menu\Programs` folder on the [Golden Image](/landing/daas-guides/daas-administrators-guide/getting-started/editing-the-golden-image.md)**,** and if it's not there, create it and save the changes.
{% endhint %}

{% embed url="<https://youtu.be/E12MTctRQTc>" %}

Next, you need to [add users.](/landing/daas-guides/daas-administrators-guide/getting-started/adding-users.md)&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/getting-started/publishing-resources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.