> 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/copy-entries-from-your-user-vault-to-a-vault.md).

# Copy entries from your user vault to a vault

Copy entries from your user vault to another vault in Remote Desktop Manager without exporting and importing files.

To be able to copy some entries stored in your user vault to another vault without doing an export/import in Remote Desktop Manager, follow the steps below.

### Permissions

Some permissions in ***Administration – System permissions*** need to be allowed for standard users:

* Copy feature: Enable the ***Export*** and ***Copy Password*** permissions on the source folder.
* Paste feature: Enable ***Import*** and ***Add*** permissions on the destination folder.

### Steps

1. Select the entries from your user vault that you wish to add to your main vault.
2. Right-click on your selection.
3. Select ***Clipboard – Copy***.
4. Make sure that the ***Change ID*** option is checked in the ***Copy Options*** window.
5. Move to your main vault, select the folder in which you wish to add your entries, then right-click on it.
6. Select ***Clipboard – Paste***.

Your entries should now be copied to the destination vault.


---

# 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/copy-entries-from-your-user-vault-to-a-vault.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.