> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/customization.md). # Customization - [How to Customize the Remote Desktop Shortcut](https://docs.plenit.com/docs-en/productos/remote-desktop/customization/how-to-customize-the-shortcut.md): Configure Windows Explorer arguments so your users open the storage unit you choose directly, without browsing manually. - [How to Customize the Avatar in Remote Desktop](https://docs.plenit.com/docs-en/productos/remote-desktop/customization/how-to-customize-the-avatar.md): Change the avatar for the whole organization or for a specific user, during deployment, from the subscription, or from the user's own launchpad. - [How to Create Templates on a Server to Reuse Them in Remote Desktop](https://docs.plenit.com/docs-en/productos/remote-desktop/customization/how-to-create-reusable-server-templates.md): Turn an already configured server into a template and reuse it in future Remote Desktop deployments to automate the configuration. --- # 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.plenit.com/docs-en/productos/remote-desktop/customization.md?ask=&goal= ``` `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.