> 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/campaigns-and-jobs.md).
# Campaigns & Jobs
Create, track, approve, and complete campaigns and jobs from the end-user and administrator views.
A **Job** is one customization of an asset. A **Campaign** groups assets under a shared schedule and can assign each asset to a specific user. Campaigns are normally available on Enterprise sites; other sites create jobs directly from assets.
***
## Creating a Campaign
1. Open **Campaigns** and click **New Campaign**.
2. Enter a name and due date.
3. Select one or more Templates, Packages, or Forms.
4. Optionally assign users from the relevant Department to individual assets.
5. Confirm the completion options and start the campaign.
When the campaign begins, BrandingUI creates jobs for its assigned assets. Assigned users receive notifications and can open their work from **Campaigns** or **Jobs**. Reminders can be sent as the due date approaches and after work becomes overdue.
{% hint style="info" %}
Only a user can create a new campaign. Admins can click Users and select a user in their organization.
Click View as in the top right. You are now able to create a new campaign.
{% endhint %}
### Finding Campaigns
Campaign lists can be sorted by relevance, start date, due date, name, and, where applicable, Department. Use the date range and search fields to narrow the list, and switch between grid and list views as preferred. Completed campaigns can be shown or hidden; deleted and expired campaigns are available through reports rather than the standard end-user list.
## Creating and Editing Jobs
A job is created when you select an asset directly or begin an assigned campaign item. Some sites also enable **Quick Jobs**, which provide a direct route from an asset to its editor.
1. Select a Template, Package, or Form.
2. Customize the editable text, images, colors, fields, or artboards.
3. Save and return later if the workflow allows it.
4. Preview the result or download a proof when available.
5. Select a completion method if choices are exposed.
6. Enter any required job name or reference and click **Finished**.
Templates may offer multiple Liquid Layout sizes or permit a custom size within administrator-defined limits. Package artboards can share content, so one change may update several output sizes. Forms collect structured data and may generate a document, send a notification, or enter approval.
### Finding Jobs
The **Jobs** page can sort work by relevance, status, submission date, or job name. Search and date filters narrow the results, while grid and list views change the presentation. Administrators see jobs across users and can use reports to include deleted or expired work.
{% hint style="info" %}
Incomplete jobs typically expire much sooner than submitted work. The source documentation describes unfinished jobs as commonly expiring after about one week, while submitted or completed jobs may be retained for up to six years. Your site's retention policy may differ.
{% endhint %}
## Approval and Completion
If approval is required, the job remains pending until every required approver at the current level responds. Later approval levels are notified only after the preceding level is complete. A rejected job includes feedback and can be revised and resubmitted when editing is allowed.
After approval, the configured completion methods run. Depending on the asset and site settings, BrandingUI may:
* Allow the user or approver to download PDF, JPEG, PNG, or other outputs.
* Notify a print provider or another recipient to download files.
* Transfer files to FTP, HTTP, email, or a connected DAM.
* Complete a Form-specific action.
If a download is missing, confirm that the job is complete, all approvals have finished, and the selected completion method permits user downloads.
## Converting Completed Jobs
Administrators can convert a completed Template or Package job into a new reusable asset. Where enabled, end-users can select **Request Conversion**, suggest a new asset name, and send a message to the administrator. Converted names may be adjusted to meet server naming requirements.
## Contact and Help
Use the built-in **Contact** page to send a question to site administrators. If Notifications does not define dedicated information-request recipients, the message goes to the **Business Email** configured in General Settings.
---
# 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/campaigns-and-jobs.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.