> 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/web-interface/vaults/entries/entry-section/attachments/view-deleted-attachments.md).

# View deleted attachments

The View Deleted Attachments tab on a Devolutions Server entry lets administrators restore deleted attachments, noting permanent deletion is irreversible.

Entries deleted attachments can be restored and managed in the entry ***View Deleted Attachments*** section of the ***Attachments***.

{% hint style="danger" %}
Deleting from the ***View Deleted Attachments*** section is irreversible.
{% endhint %}

#### Restore an Attachment

1. Click on the entry that the attachment was deleted from.

{% hint style="info" %}
To view all deleted attachments, run the ***Activity Logs*** report with the filter ***Message*** : ***Attachment deleted***.
{% endhint %}

2. Click ***Attachments***.
3. Click ***View Deleted Attachments***.
4. Select the attachment in the list.
5. Click ***Resurrect***.


---

# 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/web-interface/vaults/entries/entry-section/attachments/view-deleted-attachments.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.