> For the complete documentation index, see [llms.txt](https://docs.segments.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.segments.ai/guides/configure-label-editor/configure-rules.md).

# Configure rules

{% hint style="info" %}
[More info about how to use the warning system while labeling / reviewing](/how-to-annotate/use-the-warning-system.md)
{% endhint %}

## Configuration

Go to your dataset settings into the labeling tab. Scroll down the page to the warnings section (just after the categories section).

Here you can enable the intersecting cuboids rule and / or the cuboid dimension rules.

<figure><img src="/files/o4ICzi2ZataPyFaumoYk" alt=""><figcaption></figcaption></figure>

### Intersecting cuboids

<figure><img src="/files/QNVg2wjJBJFgs1vR7MYg" alt=""><figcaption></figcaption></figure>

Excluded groups are groups of categories that should not raise a warning when they intersect with each other. A common example is a person on a bicycle.

Excluded categories are a set of categories that the rule should not be applied to at all. Add categories here that should be ignored during the check for intersecting cuboids.

Here's an example of a configuration.

<figure><img src="/files/nepjnGnvbPX2cBNTWbSk" alt=""><figcaption></figcaption></figure>

It's also possible to configure an overlap threshold.

<figure><img src="/files/fmaxfLUgdZn95xsuKQFY" alt=""><figcaption></figcaption></figure>

### Cuboid dimensions

Configure rules that can warn users when cuboids exceed certain limits. Only fields that are filled in are checked.

This can be applied on a global scale by adding a rule without setting any categories on it.

<figure><img src="/files/05txiqjXRTbVX9h1TRRu" alt=""><figcaption></figcaption></figure>

You can also configure more granular limits for groups of categories.

<figure><img src="/files/pTy2CnM4t1yU7nzJSLhO" alt=""><figcaption></figcaption></figure>


---

# 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.segments.ai/guides/configure-label-editor/configure-rules.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.