> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/gemini-home/core-concepts/business-structure.md).
# Organization and Asset Visibility
Learn how BrandingUI models your organization using Business Units, Departments, and Category visibility rules.
BrandingUI relies on a structured organizational model to automate approval flows and restrict template visibility so that users see only the assets relevant to their specific role, region, or client.
***
## Business Structure
Administrators define an organizational tree consisting of **Business Units** and **Departments** under Profile → Global Settings → Business Structure.
{% hint style="info" %}
Departments and Campaigns are Enterprise features. SMB sites generally organize users with Business Units but create jobs directly without Department-level routing.
{% endhint %}
### Customizing Labels
By default, the platform uses **Business Unit** and **Department**. However, these labels can be renamed globally to match your organization's vocabulary under Profile → Global Settings → Business Structure → Labels:
* **Retail model**: Rename Business Units to Retailer/Franchise and Departments to Store.
* **University model**: Rename Business Units to College and Departments to Academic Department.
* **Agency model**: Rename Business Units to Client and Departments to Division.
### Hierarchy and Overrides
You can organize the tree by adding multiple Business Units, and nesting multiple Departments within each unit.
* Business Units and Departments can be reordered easily by dragging them in the admin interface.
* If your organizational layout changes, you can use Merge to merge two departments or business units.
* Each Business Unit and Department features an Options button, allowing administrators to override global preferences, such as default completion methods, approval levels, or email addresses, for specific parts of the company.
#### Inheritance of Overrides
Business Structure overrides operate on a top-down inheritance model:
1. **Fallback**: If no overrides are set at any level, the system implements the **Global Settings**.
2. **Business Unit Overrides**: Overriding a setting at the Business Unit level applies that override to all nested Departments automatically.
3. **Department Overrides**: Setting an override at the Department level overrides both the Business Unit override and the Global Settings for that specific department, enabling precise location-based or division-based customization.
4. **Asset Overrides**: Options applied to an individual Template, Package, or Form take precedence over Department, Business Unit, and Global settings.
## Asset Categories
To prevent end-users from being overwhelmed by hundreds of templates, all assets must be assigned to Categories.
{% hint style="info" %}
Any asset that has its category set to **None** will not be visible to end-users.
{% endhint %}
* Assets can be assigned to multiple Categories and Subcategories.
* Category and subcategory names are case-sensitive. For example, **Business Cards** is different from **Business cards**. They must not contain special characters like commas, asterisks, or underscores.
* **Keywords** are hidden search tags. Unlike Categories, they make assets easier to find but do not control who can see them.
## Category Visibility Rules
Administrators configure visibility rules under Users → Templates/Packages/Forms to control which categories are exposed to which users:
* **E-mail Domain matching**: Show a specific category of templates. For example, **ABCorp Assets** to any user signing in with an `@abcorp.com` email address.
* **Organizational matching**: Show templates based on the user's Department, Role, Country, or Time Zone.
* **Fallback rule**: A default category selection is shown to any user who does not explicitly match any of the custom visibility rules.
Rules can also match full or partial email addresses, custom user fields, language, or locale. If several rules match, BrandingUI uses one matching source according to database order; it does not merge every matching rule or use the visible page order. Administrators should always verify important combinations with **View As** on the Users page.
---
# 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.santacruzsoftware.com/gemini-home/core-concepts/business-structure.md?ask=&goal=
```
`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.