> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/orbit/hilfe/faq/geloeschtes-wiederherstellen.md).

# Lassen sich gelöschte Inhalte wiederherstellen?

Gelöschte Elemente, Dateien und Versionen holen Sie in powerIO Orbit aus dem Papierkorb zurück. Die Antwort nennt Tarife, Fristen und berechtigte Rollen.

Ja, in den Tarifen Starter S1, Premium P1 und Unlimited U1. Gelöschte Inhalte liegen dort im Papierkorb unter **Restore** und lassen sich bis zum Ablauf der Frist zurückholen.

## Fristen und Rollen

Die Frist beträgt je nach Tarif <code class="expression">space.vars.trash\_days\_starter</code>, <code class="expression">space.vars.trash\_days\_premium</code> oder <code class="expression">space.vars.trash\_days\_unlimited</code> Tage. Wiederherstellen dürfen die Rollen **Customer admin**, **Project admin** und **Project manager**.

Im Tarif Free gibt es keinen Papierkorb, dort löscht Orbit sofort endgültig. Die Schritte zum Wiederherstellen stehen unter [powerIO Orbit: Audit Log und Papierkorb](/hub/orbit/verwaltung/audit-und-papierkorb.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://support.powerio.com/hub/orbit/hilfe/faq/geloeschtes-wiederherstellen.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.