> 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/reference/account-types-and-labels.md).

# Account Types & Configurable Labels

Understand how account type, enabled features, and customizable labels affect what appears in BrandingUI.

BrandingUI sites do not all expose the same navigation or workflows. The account type establishes the broad feature set, while administrators can enable individual asset types and rename common terms.

***

## Account Types

<table data-search="false"><thead><tr><th>Capability</th><th align="center">Enterprise</th><th align="center">SMB</th></tr></thead><tbody><tr><td>Business Units</td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Departments within Business Units</td><td align="center">✓</td><td align="center">—</td></tr><tr><td>Campaigns</td><td align="center">✓</td><td align="center">—</td></tr><tr><td>Templates, Packages, and Forms</td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Approval workflows</td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Department approvers and overrides</td><td align="center">✓</td><td align="center">—</td></tr><tr><td>Asset-level overrides</td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Designer package access</td><td align="center">✓</td><td align="center">✓</td></tr><tr><td>Reports and email integrations</td><td align="center">✓</td><td align="center">✓</td></tr></tbody></table>

Enterprise sites support the full Business Unit -> Department hierarchy, campaign assignment, and department-specific routing. SMB sites generally use Business Units without Departments and create jobs directly from assets. Some sites use an Advanced or otherwise tailored configuration with a smaller selection of these features.

{% hint style="info" %}
Feature availability also depends on your subscription and site settings. Templates, Packages, Forms, Quick Jobs, email output, external authentication, user downloads, and designer access can each be enabled or disabled.
{% endhint %}

## Configurable Labels

Administrators can rename key terms so BrandingUI matches the language used by their organization.

| Default Label        | Example Alternatives              |
| -------------------- | --------------------------------- |
| Template / Templates | Design, Layout, Flyer             |
| Package / Packages   | Banner Set, Digital Kit, Ad Set   |
| Campaign / Campaigns | Project, Initiative, Sprint       |
| Business Unit        | Region, Brand, Retailer, Division |
| Department           | Store, Team, Office, Branch       |

Renamed labels appear in navigation, headings, help text, email notifications, search, and filters. These docs use the default terms; substitute the corresponding term shown on your site.

## What Controls Your View

The options visible to an individual user are the combined result of:

1. The site's account type and enabled features.
2. The user's assigned roles.
3. The user's Business Unit or Department.
4. Category visibility rules.
5. Global, organizational, and asset-level overrides.

An administrator can use <kbd>View As</kbd> on the Users page to verify the exact navigation, assets, and workflows available to a particular user.


---

# 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/reference/account-types-and-labels.md?ask=<question>&goal=<endgoal>
```

`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.
