> 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
In the dataset settings, rules can be configured to help spot potential issues early by raising warnings. Currently, the rules that can be added are only applicable to cuboids.
{% 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.
### Intersecting cuboids
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.
It's also possible to configure an overlap threshold.
### 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.
You can also configure more granular limits for groups of categories.
---
# 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.segments.ai/guides/configure-label-editor/configure-rules.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.
