> 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/infrastructure/providers.md).

# Providers

Providers are hypervisors or cloud-based virtualization solutions that can be added to a RAS Farm to use virtual machines as Virtual Desktops.

Please note that at the time of this writing, the Provider functionality in the RAS Management Portal is limited to viewing the available providers, hosts, and active sessions. To perform other Provider tasks, please use the desktop-based Parallels RAS Console.

## **Provider list**

To see the list of providers, navigate to **Infrastructure** > **Providers**.

To add or remove columns to/from the **Providers** table, click the gear icon and select or clear desired columns.

To perform a task, select a provider in the list and choose one of the following from the ellipsis menu:

* **Show hosted VDI desktops**: Opens the [Host list](/landing/ras-mp-guide/infrastructure/virtual-desktops-infrastructure.md) with a filter applied to show only the hosts that belong to this provider.
* **Show active sessions**: Opens the [Sessions list](/landing/ras-mp-guide/sessions.md) with a filter applied to show only session that belong to this provider.


---

# 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-mp-guide/infrastructure/providers.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.