> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/import-a-csv-file-as-a-password-list-with-hostnames.md).

# Import a CSV file as a password list with hostnames

Import a CSV file as Password list entries in Remote Desktop Manager, with the required columns, an example file, and how rows are grouped into items.

The ***Import generic CSV wizard*** can create ***Password list*** entries from a CSV file. Each row of the file becomes one item of a password list, and rows that share the same name and folder are merged into a single ***Password list*** entry.

## Prepare the CSV file

The first line of the file must contain the column headers. The wizard maps the columns by their header name, so use the headers below.

<table><thead><tr><th width="180">COLUMN</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Name of the <em><strong>Password list</strong></em> entry. All rows with the same <em><strong>Name</strong></em> and <em><strong>Group</strong></em> become items of the same entry. This column is <strong>mandatory</strong>; rows without a name are skipped.</td></tr><tr><td><strong>Group</strong></td><td>(Optional) Folder in which the entry is created. Use a backslash (<code>\</code>) to separate subfolders, for example <code>Infrastructure\Linux</code>.</td></tr><tr><td><strong>EntryType</strong></td><td>Type of entry to create. Enter <code>Password list</code> on every row. The value is not case-sensitive.</td></tr><tr><td><strong>Username</strong></td><td>Username of the item.</td></tr><tr><td><strong>Password</strong></td><td>Password of the item.</td></tr><tr><td><strong>Domain</strong></td><td>(Optional) Domain of the item.</td></tr><tr><td><strong>Host</strong></td><td>(Optional) Host or IP address of the item. A <em><strong>URL</strong></em> column can be used instead.</td></tr><tr><td><strong>Description</strong></td><td>(Optional) Description of the item.</td></tr></tbody></table>

{% hint style="warning" %}
For password lists, use the ***Username***, ***Password***, and ***Domain*** headers. The ***CredentialUserName***, ***CredentialPassword***, and ***CredentialDomain*** headers used to import other entry types do not fill in the password list items.
{% endhint %}

The ***EntryType*** value must match the name of the entry type in the language Remote Desktop Manager is displayed in. In English, this is ***Password list***.

### Example

The following file creates two ***Password list*** entries in the ***Infrastructure*** folder:

```
Name,Group,EntryType,Username,Password,Host,Description
Web Servers,Infrastructure,Password list,admin,Example-Pass-01,web01.example.local,Primary admin account
Web Servers,Infrastructure,Password list,deploy,Example-Pass-02,web01.example.local,Deployment service account
Web Servers,Infrastructure,Password list,monitor,Example-Pass-03,web02.example.local,Monitoring read-only account
DB Servers,Infrastructure,Password list,dbadmin,Example-Pass-04,db01.example.local,Database admin account
DB Servers,Infrastructure,Password list,backup,Example-Pass-05,db02.example.local,Backup job account
```

After the import, the ***Infrastructure*** folder contains:

* A ***Web Servers*** entry with three items (***admin***, ***deploy***, and ***monitor***).
* A ***DB Servers*** entry with two items (***dbadmin*** and ***backup***).

### How rows are grouped

* Rows are merged only when both the ***Name*** and the ***Group*** values are identical. The comparison is case-sensitive: ***Web Servers*** and ***web servers*** create two different entries.
* The same name in two different folders creates two separate entries.
* A single row still creates a ***Password list*** entry, with one item.
* The ***Name*** column names the entry, not the item. Imported items have no item name; you can add one afterwards in the entry properties.
* Settings that belong to the entry itself rather than to an item, such as tags or custom fields, are taken from the first row of each group.
* Rows are grouped within the imported file only. Importing a file does not add items to a ***Password list*** entry that already exists in the vault.

## Import the file

1. In the navigation pane, select the folder in which to import the entries. The folders of the ***Group*** column are created under this folder.
2. Go to ***File – Import – Import generic CSV wizard***.
3. In ***Import type***, keep ***Session***. The ***Credential*** import type only creates ***Username and password*** entries and ignores the ***EntryType*** column.
4. Select ***Open CSV file*** and browse to your `.csv` file, or select ***Paste CSV text*** and paste the content of the file. Click ***Next***.
5. Check the preview. Make sure the ***Delimiter*** is set to a comma and that ***Has headers*** is selected, then click ***Next***.
6. Validate the ***Mappings***. Each property should point to the matching column of the file, for example ***Username*** to `$Username$`. Adjust any mapping that is incorrect.
7. Click ***Finish***.
8. Review the list of entries to import, then confirm the import.

To add, modify, or remove items after the import, edit the entry or use the PowerShell cmdlets described in [Password list](/rdm/knowledge-base/knowledge-base-articles/entry-settings/password-list.md#manage-password-list-items-with-powershell).

## See also

* [Password list](/rdm/knowledge-base/knowledge-base-articles/entry-settings/password-list.md)
* [CSV import strategies and file format](/rdm/ribbon-menu-bar/file/import/import-generic-csv-wizard/csv-import-strategies-and-file-format.md)


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/import-a-csv-file-as-a-password-list-with-hostnames.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.