> 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-admin-guide/parallels-ras-21-administrators-guide/session-management/the-resources-tab.md).

# The Resources tab

The **Resources** tab in the **Sessions** category displays currently running published resources (apps and desktops).

Some of the notable columns in the list are:

* **ID**: The published resource ID (as seen in the **Publishing** category).
* **Published name**: Published resource name (as seen in the **Publishing** category).
* **User**: Session owner.
* **Session ID**: Session ID.
* **Session Host**: Session host name.
* **Source**: Session source (RDSH, VDI, RemotePC, AVD).

To perform a task on a resource, click the **Tasks** menu. Some of the tasks include:

* **Search**: Allows you to filter the list using one or more columns (e.g. User, Session ID, Session Host, etc.).
* **Show user session view**: Switches to the **Users** tab and applies a filter to display the session to which the selected resource belongs.
* **Go to published resource**: Takes you to the **Publishing** category and displays the selected resource information.
* **Show information**: Displays the resource summary info and the session information. The session information includes the same metrics as described in [**Session information**](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/session-management/session-information.md).


---

# 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/ras-admin-guide/parallels-ras-21-administrators-guide/session-management/the-resources-tab.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.