> For the complete documentation index, see [llms.txt](https://docs.kaedim3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaedim3d.com/removing-assets/delete.md).
# Delete
### Delete a step
The option to delete a step can be found in the ellipses button on the right of that version. Here's a short guide on what you can and can't delete:
#### ✅ What You *Can* Delete
* **Only the latest step** of an asset can be deleted.
* The step must be in one of the following states:
* **For Review**
* **Finished processing**
#### ❌ What You *Cannot* Delete
* **Middle steps**: Any step that is not the latest cannot be deleted.
* **Multiple steps at once**: There is no bulk delete option. Each step must be removed individually.
***
### Move asset to Trash
**To move an asset to Trash**, you must:
1. Go to the **Settings** tab of your selected asset.
2. Scroll to the bottom, and click 'Move to Trash.'
{% hint style="info" %}
All deleted assets will still be available in the Trash section.
{% endhint %}
{% hint style="info" %}
If you need to restart an asset, consider [Branching](/reviewing-assets/branching.md) and editing instead of manual deletion.
{% endhint %}
---
# 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.kaedim3d.com/removing-assets/delete.md?ask=&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.
