> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/data-management/file-filters.md).
# File filters
The "**File Filters**" feature allows you to select only files with a specific status, such as "unprocessed" or "processed". This is especially useful in workflows that require handling data based on specific conditions—such as creating a Data Job that should only include files pending processing.
With filters, you can save custom criteria and reuse them whenever needed, streamlining automation and ensuring that only relevant data is considered during query execution. All filters are created in the **Data Lake**.
When you click "**File Filters**" in the left-hand menu, you’ll see a list of all previously created filters. You can drag these filters into the editor and use them directly in a query within the **Data Warehouse**.
### File Filter Options
When you hover over a filter, the options icon (three dots) will appear. The following actions are available:
* **Manage Groups**: Add or remove groups that the filter belongs to. After making changes, click "**Done**.
* **Delete**: Permanently remove the filter. To confirm deletion, type the name of the filter and click "**Delete**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.skyone.cloud/english/skyone-studio/data-management/file-filters.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.