> 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/pdfm-ug/v27-fr-fr/guide-de-lutilisateur-de-parallels-desktop-pour-mac-27/rubriques-avancees/utiliser-les-machines-virtuelles/organiser-les-machines-virtuelles.md).

# Organiser les machines virtuelles

Si vous avez un grand nombre de machines virtuelles, la fenêtre du **Centre de contrôle** risque d'être surchargée et peu pratique.

Vous pouvez configurer le **Centre de contrôle** pour n'afficher que le minimum d'informations, soit uniquement les noms et les icônes des machines virtuelles. Pour ce faire, clique sur l’icône Parallels Desktop dans le Dock et choisissez **Affichage** > **Vue compacte** dans la barre de menus de macOS.

Si vous utilisez Parallels Desktop pour Mac Pro Edition, vous pouvez choisir le mode d'organisation des machines virtuelles. Cliquez sur l'icône Parallels Desktop dans le Dock, cliquez sur **Affichage** > **Organiser par** et choisissez la façon dont vous souhaitez répertorier les machines virtuelles.


---

# 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/pdfm-ug/v27-fr-fr/guide-de-lutilisateur-de-parallels-desktop-pour-mac-27/rubriques-avancees/utiliser-les-machines-virtuelles/organiser-les-machines-virtuelles.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.