> 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/server/knowledge-base/how-to-articles/share-an-entry-through-devolutions-server.md).

# Share an entry through Devolutions Server

Share an entry securely through Devolutions Server by sending a copy to chosen users with an optional time limit and high priority notification.

Learn how to share an entry securely through Devolutions Server.

1. Open Devolutions Server.
2. Navigate to the entry to share.
3. Right-click the entry or click the ***More options*** button (three vertical dots) next to it.
4. From the dropdown menu, select ***Send Copy***.
5. The ***New message*** window opens.
6. Choose the user(s) you want to share the entry with.
7. Write a subject and a secure message (optional).
8. If needed, set a time limit for the message’s availability, ensuring enhanced security.
9. Check the ***Send with high priority*** box to make the message appear immediately for the recipient.
10. Click **Send** to securely share the entry.
11. The recipient will receive a notification and can open the shared entry. The shared entry can be saved in the user 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/server/knowledge-base/how-to-articles/share-an-entry-through-devolutions-server.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.