Asset Workflow is the tool to govern the approval lifecycle of your creative Assets: from upload to brief, all the way to publication in Digital Assets.

With a Campaign you coordinate in a single flow who produces, who reviews, and who approves, bringing the Asset into Digital Assets only when it has passed all planned steps.

Prerequisites

To work in Asset Workflow you must have an active THRON account with access to the Asset Workflow module. Within the module, what you can do depends on how you are involved in each individual Campaign or Job:

Whoever creates a Campaign or a Job automatically becomes its main Owner, and can appoint other Owners to grant them the right to edit or delete them. Additional Owners can be users or groups, provided they already exist on the Platform.

Core concepts

Five elements make up each workflow:

How approval works

In Asset Workflow there are no predefined native approval or rejection mechanisms: you design the flow. You define the stages representing the phases of your process and the transitions that move Assets from one stage to another.

As a result:

• An approval is a transition advancing the Asset to the next stage.

• A rejection is a transition taking it back to a previous stage, for example from Approval back to Production.

• The button text that Participants see on the Asset is what you defined on the transition.

This flexibility allows the module to adapt to any process: before creating the Job, design the workflow you want to replicate, including return paths.

1. Access Asset Workflow

From the area selector at the top left, select Workflow.

On the homepage you will find the list of all Campaigns where you are involved as an Owner or Participant.

2. Create a Campaign

This action is restricted to Campaign Owners.

1. Click on + New Campaign.

2. Enter a name for the Campaign, for example "SS25 Launch".

3. Confirm. The Campaign is ready to host Jobs.

3. Create a Job and configure the flow

To create a Job you must be an Owner of the current Campaign. Click on + New Job, then complete the four configurations below.

Define stages and transitions

Drag Stages onto the canvas and connect them with Transitions. For each transition, choose the rule that triggers it:

• Manual action: a user clicks the transition button.

• Automated condition: the system moves the Asset automatically upon reaching a threshold, such as a minimum number of Likes or Dislikes.

Choose transition destinations

Each transition can move the Asset in three directions:

• Another stage in the same Job: the Asset advances or moves back, remaining in the Job.

• The first stage of another Job: the two workflows chain together. Useful when production is split into phases managed by separate teams, such as a photoshoot Job followed by a post-production Job.

• A folder in Digital Assets: the Asset is published to the chosen folder and leaves the Job. This is the standard method to make content available for distribution.

As a destination you can choose either a root folder or a subfolder, but only among those you have visibility on. If the transition replaces content already in Digital Assets, you also need edit permissions on that content.

Add Participants

Invite the users or groups who will work on the Job. They must already exist on the Platform. For each one, choose the access level, which applies to all Assets in the Job:

All Participants see Assets in every stage of the Job, regardless of their access level.

For Participants with edit permissions you can further configure, stage by stage, whether they can:

• Download content.

• Upload content, either as a new Asset or as a new version of an existing one.

• Edit general Asset information, specifically name and description.

Upload the brief

This step is optional and managed by the Owner. Attach guidelines or briefs in any format-such as PDF, Word, or PowerPoint-in the Attachments section. All Participants can download them in their original format.

4. Upload Assets

From the Job details view, click on Upload Asset and select the files. The Asset enters the first stage of the workflow and becomes visible to all Job Participants.

5. Advance Assets through the flow

Open an Asset to view its details. Based on your access level and the rules configured on the Job, you can trigger transitions in three ways.

Use the transition button

Click the button corresponding to the transition you want to trigger. The button text is defined by the Owner during setup, so it varies across Jobs.

When an Asset reaches a transition pointing to A folder in Digital Assets, it is published to that folder and removed from the Job. If the destination is another Job, the Asset enters the first stage of that Job and the workflow continues there.

Vote with Like and Dislike

If the Owner configured an automated rule, the Asset moves when a specified number of users click Like or Dislike. Each vote automatically creates a comment on the Asset with the name of the voter.

Comment on an Asset

Open the comments panel from the Asset details view to provide feedback on requested changes. Each comment includes the author, date, and text, and can contain up to 1,000 characters. There is no limit on the number of comments per Asset.

Comments stay with the Asset: they remain visible across all stages and even when the Asset is transferred to another Job.

6. Track progress

From the Job view you can see which stage each Asset is in and what actions are required. Filter by stage to quickly identify pending content.

7. Receive notifications

The system notifies you via email when events occur in Jobs you are involved in, eliminating the need to manually check the Platform. Notifications come in three types:

You receive a single consolidated email per cycle covering all relevant Jobs. The default update notification interval is 2 hours and may differ on your account: to check or modify it, contact your THRON dedicated account.

## In-depth articles
- 
Product Workflow: create and manage a job
- 
Create the folder tree
- 
Folder permissions: how they work
- 
Upload your Assets in THRON

Need help?

For technical issues, write to support@thron.com.