> 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/bannersui/core-concepts/work-by-role.md).

# Work by Role

Understand what designers and users own when creating packages and customizing jobs.

BannersUI separates reusable template work from campaign-specific production work. Designers build and maintain packages. Users customize jobs created from those packages.

Package locks protect the structure and brand decisions that designers approve. A user's available controls depend on their role and those locks.

***

## Ownership at a glance

| Area     | Owned by       | Used for                                        |
| -------- | -------------- | ----------------------------------------------- |
| Package  | Designer       | Reusable template setup and management.         |
| Job      | User           | Campaign-specific customization from a package. |
| Artboard | Package or job | One required size or layout.                    |

## Designer workflow

Designers prepare reusable packages for campaign teams. They control the template structure and define what users can customize.

Typical designer tasks include:

* Import a PSD and review the resulting artboards and layers.
* Add artboards, presets, brand resources, animation, and output settings.
* Configure layer visibility and content, position, and property locks.
* Save or publish the package through the host workflow.

Use package editing when a request changes the template itself. This includes adding banner sizes, changing locked creative, or updating shared brand assets.

## User workflow

Users customize a job for one campaign or request. A job preserves the package structure while allowing approved changes.

Typical user tasks include:

* Update unlocked text with campaign copy.
* Replace approved images or videos.
* Adjust unlocked placement and styling.
* Preview each artboard and finish the job.

Use job editing when the request applies to one campaign. Job changes do not alter the reusable package.

## Handoffs and editing boundaries

Users should contact the package designer when a change affects the template or a locked item. The designer can update the package or create a suitable variant.

| Request                                      | Best owner | Where to work |
| -------------------------------------------- | ---------- | ------------- |
| Change a campaign headline or approved image | User       | Job           |
| Add a banner size or revise a shared layout  | Designer   | Package       |
| Change locked branding, fonts, or animation  | Designer   | Package       |

{% hint style="info" %}
An unavailable control usually indicates a content, position, or properties lock. A hidden layer or locked group can also prevent editing.
{% endhint %}

## Common scenarios

* **Update media:** Edit the unlocked layer in the job. Shared content can appear on several artboards, so review every affected size after making changes.
* **Change one artboard layout:** Use object-level controls for the selected artboard when they are unlocked. Ask the designer if the layout requires a structural change.
* **Add a new size or revise the template:** Ask the designer to update the package. This keeps the package reusable and ensures future jobs include the new layout.
* **Cannot select or change an item:** The layer may be locked, hidden, or inside a locked group. Ask the package designer to make the required change or expose an approved control.

***

## Related guidance

See [Concepts and Terminology](/bannersui/core-concepts/core-concepts.md) for definitions of packages, jobs, artboards, layers, and objects.

See [Packages, Jobs, and Artboards](/bannersui/guides/packages-jobs-and-artboards.md) for editing guidance. See [Layers, Locks, and Roles](/bannersui/guides/layers-locks-and-roles.md) for lock behavior. Use [Role Capability Matrix](/bannersui/reference/role-capability-matrix.md) for detailed standard permissions.


---

# 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/bannersui/core-concepts/work-by-role.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.