> 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/tag-groups/tag-group-settings.md).

# Tag Group Settings

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

## Overview

Tag Group settings will be dependent on the selected [Response Mode](/getting-started/response-modes-explained.md) and other [Active Folder](/getting-started/organisation-structure/folders/active-folders.md) settings.

## Generic Tag Group Settings

These are settings available across more than one of the Response Modes.

### Tag Group Status

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

Changes the Status of the Tag Group and the effective status of the Tag Codes underneath. Options are :&#x20;

**Active :** Tag Codes under the Tag Group are Active.&#x20;

**Inactive :** Tag Code response is 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 'tg\_inactive' error will be returned.

**Delete :** Will delete the Tag Group. All Batches need to have been deleted to delete a Tag Group.

### Chip Count Enabled

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

This will enable the display of the Chip Count within the interface. Important : Read the notes on the difference between between [Chip Count and Scan Count](/explainers/chip-count-vs-scan-count.md).&#x20;

### Tag Group Name

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

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

### Extended Data Defaults

*<mark style="color:orange;">Tag Group Data Panel > Extended Tab</mark>*

Allows the setting of default data for any [Extended Data](/features/meta-data/extended-data.md) fields you have created (at the Active Folder level). Any data entered here will automatically be inherited by all Tag Codes within this Tag Group unless specifically set at the Tag Code level.&#x20;

Extended Data defaults can be included in the Response either using [Subtags ](/features/subtags.md)or [Data Merge](/features/datamerge.md). To include this data in a Data Merge response, you also need to allow this on the *<mark style="color:orange;">Active Folder > Folder Function Panel > Response Tab</mark>*.

## Tag Group Functions

### Ruleset

*<mark style="color:orange;">Tag Group Function Panel > Ruleset Tab</mark>*

You can create Rules here to change how tags will respond. Rules created here will apply to all tags created under this Tag Group but you can also break the link by created Tag Code specific rules if you choose.&#x20;

{% hint style="warning" %}
You need to set a Default [Redirect destination URL](/using-redirect-mode/redirect-basics.md) or select a Default Template or your tags will have nowhere to go when scanned !
{% endhint %}

{% content-ref url="/pages/vi6PgLwhie5adMmP9eCF" %}
[Rules](/features/rules.md)
{% endcontent-ref %}

### Clusters

*<mark style="color:orange;">Tag Group Function Panel > Clusters Tab</mark>*

Clusters allow grouping of Batches. Clusters for Batches under this Tag Group can be created here. Cluster names can also be dynamically included in Redirect links or Direct Response templates.&#x20;

{% content-ref url="/pages/UDkWXDuqB8FTPxTEmnBM" %}
[Clusters](/advanced-features/clusters.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 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.ixkio.com/getting-started/organisation-structure/tag-groups/tag-group-settings.md?ask=<question>&goal=<endgoal>
```

`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.