> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/products/catalog/batch-actions/edit-attribute-values/remove-values.md).
# Remove values
This action can be performed only with file, gallery, multi-select, and product relation type attributes. It removes the values you choose and keeps the others. To add an attribute, drag it from the ***Product attributes*** panel on the left and drop it on the ***Add attribute*** field. In our example, it will be a multi-select attribute, ***Promotional Label***.
Click on the attribute field, tick the values you wish to remove and click on ***Ok***. You need to know which attribute value you wish to remove, as the system will not show you the current one.
The chosen values will appear in the form.
Click on ***Save changes*** to proceed. A final confirmation window will appear, allowing you to confirm with ***Start batch action*** or abort with ***Cancel***.
---
# 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://usermanual.ergonode.com/products/catalog/batch-actions/edit-attribute-values/remove-values.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.
