> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/using-rules/organize-rules.md).

# Organize rules

Use labels and rule sections to keep complex rule setups organized.

Use labels and rule sections to make large rule setups easier to scan and maintain.

### Add labels

Labels help you identify related rules. You can use the same labels in every project in your Channable account.

{% stepper %}
{% step %}

#### Select the rules

1. Go to **Rules** in your channel.
2. Select the checkboxes for the rules you want to label.
3. Click **Rule labels**.
   {% endstep %}

{% step %}

#### Create the label

1. Click **New label**.
2. Enter a name in **Name**.
3. Choose a color in **Color**.
4. Click **Create**.
   {% endstep %}
   {% endstepper %}

{% hint style="warning" %}

#### Important

Deleting a label removes it from every rule in your Channable account.
{% endhint %}

### Use rule sections

Create rule sections to group related rules in the **Rules** step.


---

# 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://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/using-rules/organize-rules.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.
