> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-business-rules/how-to-set-up-business-rule-to-trigger-for-business-units.md).
# How to set up business rule to trigger for business units
When designing a business rule, you can set a condition for the trigger. In this scenario, the condition will be business units. This condition checks to see if the entity that triggered has any relation to or is owned by a business unit.
In this quick guide we will create a business rule that will check if the entity has any relation to the 'Asia' business unit.
{% hint style="info" %}
Don't have any business units set up yet? Learn [how to do that in this guide](/reference/settings/data-governance/business-units.md).
{% endhint %}
### Setting the condition
First, create a business rule and add a trigger that you would like to use. In this scenario we will be using the 'Product value has changed'-trigger.
When you have selected a trigger, click the 'Add condition'-button.
Inside the business rule creator window
Inside the context window, you will be presented with all the available conditions for that specific trigger.
Click 'Business units'.
The list of all available condition for our trigger
As mentioned in the beginning, we want to check if the product has any relation to the 'Asia'-business unit.
So, we click the 'Add business unit', select 'Asia' and set the relation type to 'Has any relation'.
Setting the business unit condition
Click 'Confirm'.
You can add any action you want to inside the condition block. We want to create a task whenever this condition is met, so we can check up on the change made.
The final stage of the business rule we've created
Now, whenever this business rule triggers, it will check the condition which checks if the entity has any relation to the specified business unit(s). If so, it will create a new task, and assign the colleagues from Asia to it so that they can check up on the change.
---
# 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.struct.com/tutorials/guides/how-to-use-business-rules/how-to-set-up-business-rule-to-trigger-for-business-units.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.
