> 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/getting-started/admin-onboarding.md).
# Administrator Onboarding
A guided walkthrough for BrandingUI site administrators to set up their site configuration, organization, and completion workflows.
Use this guide to configure your BrandingUI site in a practical order.
{% hint style="info" %}
Click the question-mark icon on a settings page to open contextual help. You can return to administration guidance from the account menu.
{% endhint %}
***
## Before you start
Confirm these choices before configuring BrandingUI:
| Area | Decide |
| ---------------------- | ------------------------------------------------------------------------ |
| Users and approvals | Identify site administrators and approval owners. |
| Organization structure | Confirm whether Business Units and Departments match your organization. |
| Asset types | Decide whether users need Templates, Packages, Forms, or a combination. |
| Completion workflow | Define output delivery methods, approval requirements, and destinations. |
## Recommended Setup Checklist
After designers upload initial assets, configure the site in this order:
1\. **General and Contact Settings:**
* Navigate to General Settings.
* Fill in all required fields marked with an asterisk (`*`).
* Enter your Business Email under **Contact** — this serves as a critical fallback address for user inquiries and system notifications.
* Set up **Site & Editor Locales** to control default languages and number/date formats.
2\. **Notifications and CC Options:**
* Go to Notifications Settings.
* Set email addresses for receiving new account approval requests and contact form submissions.
* Enable or disable reminder emails and frequencies for pending jobs and campaigns.
* Run a **Test Email** to verify your SMTP delivery is working and check for any flagged bad email addresses.
3\. **Business Structure:**
* Go to the Business Structure page.
* Customize your organizational labels (e.g. Division/Region vs Department/Store).
* Input your Business Units and add the respective Departments under each.
* Note the **Options** buttons next to each unit/department — these allow you to override global settings (such as default completion methods or specific approvers) on a department-by-department basis.
4\. **Categorize Assets:**
* Visit your **Assets** pages (Templates, Packages, or Forms).
* Check one or more assets and select Change Categories to organize them into user-facing categories and subcategories.
{% hint style="info" %}
*Note: Assets with "None" as their category will not be visible to end-users.*
{% endhint %}
* Optionally, select Change Keywords to assign hidden search tags, or Change Options to set asset-level workflow overrides.
5\. **Add and Authorize Users:**
Go to the Users page. You can add users individually, import them in bulk via an Excel (`.xlsx`) file, or configure automatic account creation rules.
* Assign each user their appropriate role:
* **User**: Can customize templates/forms and manage campaigns/jobs.
* **Administrator**: Full administrative settings access.
* **Approver**: Authorized to sign off on submitted jobs.
* **Designer**: Can create and modify packages.
* **Guest**: Temporary access role that automatically expires.
* Go to the Users or Categories settings to specify exactly which asset categories each user or email domain can view.
* Use the View As button on any user to sign in as them and test exactly what they see.
6\. **Define Job Completion Methods:**
* Go to the Completion settings page to define what happens when a user selects Finished on an asset.
* Create your specific output methods (FTP uploads, email transfers, or local end-user downloads).
* Specify whether each completion method requires approval and define the assigned approver email addresses for each level of the workflow.
## Theme settings
Administrators can customize the styling of their workspace dynamically under Global Settings → Theme Settings. Colors are arranged logically to guarantee clear, high-contrast user interfaces:
* **Header Settings**: Define your **Header Background Color** and **Header Text Color** to control the main banner appearance.
* **Search Field Settings**: Define the **Search Field Color** and **Search Text Color** to manage the search bar design.
{% hint style="info" %}
*Note: The system checks your selections and alerts you if a combination (like white text on a white background) is illegible.*
{% endhint %}
## Advanced admin tools
Once your basic workspace is running, take advantage of these administrative shortcuts:
* **Convert Jobs back to Assets**:
* On any completed job details screen, select the three-dot action menu.
* Select Convert Job to Package/Template.
This takes the user's customized design output and copies it as a brand-new, reusable base template, preserving edits for future organizational campaigns.
* **Restore Dismissed Messages**:
* navigate to your user avatar menu
* Select Dismissed Messages to view and restore any cleared notices.
## Detailed administration guides
Continue with the topic that matches your next setup task:
* [**User and Access Administration**](/gemini-home/guides/user-administration.md): Account requests, imports, automatic rules, roles, and Category visibility.
* [**Asset Administration**](/gemini-home/guides/asset-administration.md): Templates, Packages, Forms, Keywords, Categories, and overrides.
* [**Site Configuration**](/gemini-home/guides/site-configuration.md): General settings, submissions, notifications, PDF presets, reports, DAM, and email integrations.
---
# 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/getting-started/admin-onboarding.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.