> 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/pd-ag/parallels-desktop-licensing-guide/managing-subscriptions-licences-and-seats/exporting-a-computer-list-to-a-file.md).
# Exporting a Computer List to a File
To export a computer list to a CSV file, do the following:
1. If necessary, filter the list by clicking the **Computers** drop-down menu and selecting from **Active**, **Deactivated**, or **Blacklisted**. Note that only the computers that are displayed in the list can be included in the file.
2. Select one or more computers that you want to include in the file. To select all computers, select the checkbox on the table header.
3. Click the **Actions** drop-down menu and choose **Save List to CSV File**.
---
# 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.parallels.com/landing/pd-ag/parallels-desktop-licensing-guide/managing-subscriptions-licences-and-seats/exporting-a-computer-list-to-a-file.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.
