> 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/designer-workflows.md).

# Designer Workflows

Upload InDesign Templates and build multi-artboard Packages from Photoshop or connected DAM files.

Designers create the source assets that end-users customize. Templates originate in Adobe InDesign through PrintUI; Packages originate in Photoshop PSD files through BannersUI. Designer access does not automatically grant BrandingUI administration unless the user also has the Administrator role.

***

## Uploading Templates from InDesign

You need Adobe InDesign, the PrintUI management panel extension, and suitable design-platform credentials.

1. Build the document in InDesign.
2. Use the PrintUI panel to identify editable text frames, replaceable image frames, allowed colors, and layout variations.
3. Upload the Template to the BrandingUI site through the panel.
4. Ask an administrator to assign categories, keywords, and workflow options.
5. Open a test job and verify every intended edit and output.

Use simple, stable frame names for Variable Data Printing and user-profile prepopulation. For resizable Templates, configure Liquid Layout and unlock the Background layer before upload.

## Creating Packages from Photoshop

Prepare one or more PSD files using clear names with standard letters, numbers, hyphens, and underscores.

1. Open **Packages** and click **Create Package**.
2. Upload PSD files or browse a connected DAM source.
3. Add up to 10 source files in one Package-creation operation.
4. Name the Package and review the generated artboards.
5. Configure editable text, images, colors, layers, and shared content.
6. Save and use **Test** to open the end-user Package editor.

Each artboard represents a format or output size, such as an Instagram post, Facebook cover, or web banner. Shared content links related artboards so a user change can update multiple outputs at once.

## Managing Artboards

From the Package detail page, designers can:

* Browse artboards in a carousel or list.
* Set output format and dimensions.
* Link shared content between artboards.
* Add PSD files or remove obsolete artboards.
* Preview individual artboards and generated output.

Before publishing, confirm that previews render, required fields are editable, locked elements remain protected, and each artboard produces the expected format and size.

## Modifying and Cloning Packages

Select **Modify** to add or replace PSD files, reconfigure artboards, or update Package settings. BrandingUI warns that changing an asset with associated jobs may affect those jobs. The warning can be toggled through the avatar menu.

Select **Clone** when a new Package should begin with an existing configuration but evolve independently. After modifying or cloning, use **Test** before assigning the Package to end-users.

## Working with a DAM

When LinkrUI and one or more DAM providers are configured, designers can browse and search an embedded DAM panel during Package creation and import PSD source files directly. Completed job outputs can also be uploaded to a configured DAM destination, with upload history recorded on the job.

<figure><img src="https://2311341321-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMh8JTeMDEDu2k0wboe1d%2Fuploads%2FjixGGl0gSFziTQBpMDmK%2Fimage.png?alt=media&amp;token=232a0572-e3e0-47c8-a834-92ddc99ef68e" alt=""><figcaption></figcaption></figure>


---

# 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/designer-workflows.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.