> 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/about-parallels-daas.md). # About Parallels DaaS Parallels Cloud is a platform that allows IT organizations and users to use various cloud-based solutions offered by Parallels. Parallels DaaS is a Parallels-assembled and hosted cloud-based Desktop as a Service (DaaS) solution that provides a virtualization control plane for IT organizations to deploy their virtual workloads, desktops, and applications that can be accessed from any user from any device. It separates the control plane from the data plane, which provides superior security, scalability, and performance. Parallels DaaS consists of two services: * Parallels DaaS Management Portal for managing users and resources * Parallels DaaS User Portal for accessing resources This guide explains how to use Parallels DaaS Management Portal. We encourage you to send us feedback about your experience as described in the [**Providing feedback**](/landing/daas-guides/daas-administrators-guide/providing-feedback.md) section. To access Parallels DaaS, visit: [https://daas.parallels.com](https://daas.parallels.com/) or --- # 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/about-parallels-daas.md?ask=&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.