> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/insights-and-rules/entitlement-rules-and-labels/setup-rules-and-labels.md).

# Setup Rules and Labels

## Overview

In this article we will show you how to setup various rules while creating the appropriate labels to identify findings within your action center. This will hep proactive notification of potential risks by setting up filters and associated rules within BalkanID. Rules are "and" / "or" rules to ensure that coverage, across your integrated systems, is accurately captured.

## Creating a Rule <a href="#h_01hq330pt61btqjrxwktfj3rry" id="h_01hq330pt61btqjrxwktfj3rry"></a>

1\. To add an rule, you must first create filters that help define the entities you wish to create the "and" / "or" rules for. To start, create and save a filter from the *Configure Group* -> *Users* -> *Filters* page.

<figure><img src="https://content.gitbook.com/content/bVGYwk8aSk5yI1GDPEW9/blobs/dG4QnwzVMhRZZIcRfdip/image.png" alt=""><figcaption></figcaption></figure>

2\. Once Filters have been saved, click on the **Rules** Tab within the Rules and Playbooks Page and select **Create Rule** as shown below:

<figure><img src="https://content.gitbook.com/content/bVGYwk8aSk5yI1GDPEW9/blobs/D9F8pm2w882ZYqUB6ogI/image.png" alt=""><figcaption></figcaption></figure>

3\. In the **Setup Rule** side panel, type in the name of the rule and select the filters that apply to this rule. Additionally, select if this is an "AND" or an "OR" rule. Once that is complete, save the rule so you can start getting notified on identities that violate this rule.

<figure><img src="https://content.gitbook.com/content/bVGYwk8aSk5yI1GDPEW9/blobs/8baWpS8CmGrpPbQjFutT/image.png" alt=""><figcaption></figcaption></figure>

4\. You may select from a pre-defined set of labels. This will help the action center user understand not just what rule has been violated, but also what risk the finding poses.

<figure><img src="https://content.gitbook.com/content/bVGYwk8aSk5yI1GDPEW9/blobs/yGtcYntkouw72NTZgEWM/image.png" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/insights-and-rules/entitlement-rules-and-labels/setup-rules-and-labels.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.