> 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/guides/asset-administration.md).

# Asset Administration

Manage Templates, Packages, Forms, categories, keywords, and asset-level workflow overrides.

Administrators manage reusable Templates, Packages, and Forms from their respective asset pages. The enabled asset types depend on the site's account and General Settings.

***

## Finding and Reviewing Assets

Use search, category, and subcategory filters to narrow large lists. Template lists can also filter assets with or without categories, assets with option overrides, selected assets, and recently added assets. If a recent upload or newly created Package does not appear, select <kbd>Refresh the list</kbd> from the three-dot menu.

## Categories and Keywords

Categories control **visibility**; keywords control **searchability**.

* Any asset assigned to category **None** is hidden from end-users.
* An asset can belong to multiple categories and subcategories.
* Category and subcategory names are case-sensitive.
* Names must not contain commas, asterisks, or underscores.
* Keywords are hidden search tags and do not grant access.

Select assets and use **Change Categories** or **Change Keywords** at the bottom of the screen. Category names can be renamed from the asset page's three-dot menu. After a major rename, review user-category rules to confirm that access still works as intended.

## Asset Options and Overrides

Use **Change Options** to give selected assets behavior that differs from inherited defaults. Common override areas include approvals, completion methods, editor behavior, submission controls, and display options.

By default, BrandingUI applies settings from most specific to least specific:

1. Asset overrides.
2. Department overrides on Enterprise sites.
3. Business Unit overrides.
4. Global settings.

Only checked settings override the inherited value. Assets with overrides display an information icon in the list. Use **Remove all options** to clear asset-specific values.

{% hint style="info" %}
Enterprise sites can override both organizational and global values per asset. SMB sites can override global values per asset without Department-level settings.
{% endhint %}

## Managing Templates

Templates are created in Adobe InDesign and uploaded with the PrintUI management panel. Administrators can categorize them, add keywords, and override their approval, completion, editor, and submission behavior.

Designers use the PrintUI panel to define editable text and image frames, color constraints, and layout variations before upload. A resizable Template must use InDesign Liquid Layout on every page and keep all Background-layer pages unlocked.

For spreadsheet-based personalization, see [**Variable Data Printing**](/gemini-home/guides/variable-data-printing.md).

## Managing Packages

Packages are BannersUI assets created from Photoshop PSD files. Each PSD can become an artboard for a particular channel or output size. Administrators manage Package categories, keywords, options, and availability in the same way as Templates.

Package changes may affect associated jobs, so BrandingUI presents a warning before modification. Designers can suppress or restore that warning from **Show Modify Warning** in the avatar menu. Test changed Packages before making them broadly available.

## Managing Forms

Forms are created directly in BrandingUI with **Create Form**. They must first be enabled in General Settings under <kbd>Profile</kbd> → <kbd>Global Settings</kbd> → <kbd>General</kbd> → <kbd>Options</kbd> → <kbd>Assets</kbd>. Forms support categories, keywords, asset overrides, approval, and Form-specific completion behavior, but do not use the same output file and email options as Templates and Packages.

## Post-Change Checklist

After changing assets or categories:

1. Refresh the asset list and confirm the expected category and override indicators.
2. Use <kbd>View As</kbd> to confirm that representative users see the correct assets.
3. Start a test job and verify editor controls, approval routing, completion methods, and output.


---

# 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/guides/asset-administration.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.