> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/mover-rechazar-eliminar.md).

# Move/Reject/Delete

It can be done, with the file selected in the list (right panel), in one of the following two ways: 1. From the “*Operations –> File -> Reject/Move/Delete”*

2. The context menu (right mouse button).

Allows the selected file to be taken out of the workflow, moving it to another directory or even deleting it. This operation is recorded in the log. Only users who have been granted the corresponding permission in the profiles can perform it.

The dialog is displayed:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/1OzudrwJhgdq3BU25VWh/image1.png)

The file can be deleted using the “*Delete*” or moved to another directory using the “*Move*” button. If a directory for rejections has been specified in the application, it will be displayed. In any case, the “…” button can be used to choose another location. Editran/FF does not have any automation to recover those files and return them to their original location.


---

# 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.editran.onesait.com/documentacion-editran/publico-editranff-v6.2-windows-en/usuario-de-onesait-ecosystems-editran-ff/operaciones-principales-sobre-los-ficheros/mover-rechazar-eliminar.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.