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

# Afficher les pièces jointes supprimées

L'onglet Afficher les pièces joints supprimées d'une entrée Devolutions Server permet aux administrateurs de restaurer les pièces jointes supprimées, en notant que la suppression permanente est irréve

Les pièces jointes supprimées des entrées peuvent être restaurées et gérées dans la section ***Afficher les pièces jointes supprimées*** de l'entrée dans ***Pièces jointes***.

{% hint style="danger" %}
La suppression à partir de la section ***Afficher les pièces jointes supprimées*** est irréversible.
{% endhint %}

#### Restaurer une pièce jointe

1. Cliquer sur l'entrée de laquelle la pièce jointe a été supprimée.

{% hint style="info" %}
Pour afficher toutes les pièces jointes supprimées, exécuter le rapport ***Journaux d'activité*** avec le filtre ***Message*** : ***Pièce jointe supprimée***.
{% endhint %}

2. Cliquer sur ***Pièces jointes***.
3. Cliquer sur ***Afficher les pièces jointes supprimées***.
4. Sélectionner la pièce jointe dans la liste.
5. Cliquer sur ***Ressusciter***.


---

# 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/fr/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.