> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c150/c158/q509.md).

# How do I empty the trash?

## Report and Run: Cloud and Integrate

You can [empty the trash](/manual/readme/content/trash/empty-the-trash.md) from the Report and Run: Cloud web portal. This will remove all items in the trash at one. 

From the Report and Run: Integrate mobile app, you can [delete individual items](/manual/report-and-run-integrate/content/trash/delete-from-trash.md) from the trash. 

## Report and Run: Offline

Since Report and Run: Offline does not have cloud storage, the app does not have a trash can. Your files are stored locally on your device. 

When you delete reports in Report and Run: Offline, they are instantly deleted and cannot be recovered.

## Related 

* [Article: Empty the trash in the Report and Run: Cloud web portal](/manual/readme/content/trash/empty-the-trash.md)
* [Article: Remove an item from the trash in the Report and Run: Cloud web portal](/manual/readme/content/trash/remove-an-item-from-the-trash.md)
* [Article: Recover an item from the trash in the Report and Run: Cloud web portal](/manual/readme/content/trash/recover-an-item-from-the-trash.md)
* [Article: Delete from trash in Report and Run: Integrate](/manual/report-and-run-integrate/content/trash/delete-from-trash.md)
* [Article: Restore from trash in Report and Run: Integrate](/manual/report-and-run-integrate/content/trash/restore-from-trash.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://docs.reportandrun.com/manual/faq/c150/c158/q509.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.