> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-5-settings/editor-3/5.7-business-units-bu.md).
# 5.7 Business Units (BU)
* A **Business Unit** is a structural category used to organize departments/regions within the platform. Determinate a business unit to the features (like banners, products) or associate operational roles to the affiliates helps business’s organization (e.g., Internal, LATAM, GCC)
* The **Root** is the top-level Business Unit in the hierarchy. All other units are created under it, either directly or as nested sub-units. It serves as the starting point for the organizational structure.
{% hint style="info" %}
Choosing Root as a BU allows to all BU see the product (e.g., a marketing tool), includes all
{% endhint %}
### **Create a Business Unit**
* Navigate by the **left Sidebar Menu** and click on the **Organization > Manage Business Units**
* Click the **Create New Business Unit** button. A popup window will appear, to complete:
* Choose the **Business Unit Name**
* Select the **Parent Business Unit**, which means the Business Unit which englobes the new Unit.
* Select the **Brand**
* Add a **Description**
* Choose a **default Deal**
* Optionally, select an allowed **Affiliate Payment Methods**
* Click on **Save** to create the new Business Unit
### **Affiliates Acquisition of their Manager’s Business Unit**
* When a manager is assigned to an affiliate, the affiliate automatically inherits the business unit associated with that manager
---
# 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://track360.gitbook.io/track360/section-5-settings/editor-3/5.7-business-units-bu.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.
