> For the complete documentation index, see [llms.txt](https://docs.ixkio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixkio.com/getting-started/organisation-structure/batches/batch-settings.md).

# Batch Settings

Organisation Folders > Active Folders > Tag Groups > <mark style="color:green;">**Batches**</mark> > Tag Codes

## Generic Batch Settings

### Batch Status

*<mark style="color:orange;">Batch Detail Panel > Settings Tab</mark>*

Modifies the status of the Batch. Options are :&#x20;

**Active :** Normal function.&#x20;

**Inactive :** Tag Codes within this Batch are disabled.  For both Redirect and Direct Response Mode, any request for Response (ie, a tag scan directing to ixkio), will show a blank page. No message is provided. For API Response Mode, a 'batch\_inactive' error will be returned.&#x20;

**Delete :** Will delete the Batch. A prompt will be given to confirm. This action cannot be reversed.&#x20;

### Batch Name

*<mark style="color:orange;">Batch Data Panel > Core Tab</mark>*

This changes the interface name for the Batch. This name can also be included in the Response using [Subtags](/features/subtags.md).

### Encoding Data

*<mark style="color:orange;">Batch Function Panel > Encoding</mark>*

Encoding URL for Tag Codes within the Batch can be downloaded as a CSV file. The CSV also contains XUID Tag Codes and any [CUID](/features/meta-data/core-data.md#custom-uid-cuid) entered for reference purposes.&#x20;

### Associate Data

*<mark style="color:orange;">Batch Function Panel > Associate</mark>*

The Associate Data feature can be used to upload CUID, UID or default Response data via CSV for all of some of the Tag Codes within a Batch.&#x20;

{% content-ref url="/pages/Ea5GmQw4cIVwYsbP0WUr" %}
[Associate Data](/features/associate-data.md)
{% endcontent-ref %}


---

# 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.ixkio.com/getting-started/organisation-structure/batches/batch-settings.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.