First steps with THRON WORKFLOW

Business Case:

KPI to be measured

Bookmark this resource Follow

Ask a question

Was this article helpful? 0 out of 0 found this helpful

THRON WORKFLOW is the expansion dedicated to the design and managing of content approval workflows in a completely autonomous and no-code modality.

THRON WORKFLOW enables companies and agencies to improve and streamline the content creation processes, maximize the efficiency and productivity of marketer teams, agencies, and creatives and efficiently collaborate with users, on the same tool, removing the exchange on multiple external systems.

With THRON WORKFLOW you can:

  • create and manage approval workflows on any kind of content and creativity, never leaving the core platform
  • design personalized workflows according to your specific needs or projects, in complete autonomy, thanks to the no-code builder
  • upload, update and deliver approved content among your brand digital channels, directly from THRON DAM PLATFORM, avoiding integrations costs and duplications.

Main entities of THRON WORKFLOW

 

The main entities of THRON WORKFLOW, defined below, are:

 

 

Campaign

A Campaign represents a set of interrelated activities, with a common goal. Campaigns are constituted by a series of Jobs.

Here below you can find different examples of Campaigns, according to your specific needs or use case:

  • In case you are a company, you can create a new Campaign, for example, for the “Launch of a new product”. In this case, the Campaign will collect all the activities (represented by Jobs) aimed at managing the production and approval of the various materials and creativities to support the launch of the new product
    • In case you manage a multi-brand company, you can create different Campaigns for different brands and projects
  • In case you are a creative agency working with different clients, you can create one (or more) Campaigns for each Client. In this case, the campaign will collect all the activities of content production (represented by Jobs) you need to work for a specific client. You can assign specific permissions to your clients to give them access and visibility only to their projects: in this way, you can collaborate with them and get feedbacks with no need of external tools.

 

 

Job

Jobs are the specific tasks part of a Campaign and allows you to define which kind of workflow your assets need to follow before they can be considered finalized for publication. When you create a new Job, you can define a specific workflow that will be valid for all the assets uploaded in that specific Job. Jobs are made of Stages, Transitions and Rules.

 

 

Stage

Stages represent the various steps of a production and approval workflow as well as the different possible statuses of an asset. Examples of Stages can be Brief, Production, Approval, Publishing but you can decide which names giving to assets during the Job Configuration.

 

 

Transition

A Transition represents the progress of an asset from one phase to another of a workflow.

A Transition can move an asset:

  • From a Stage to another Stage within the same Job
  • From a Stage to the start Stage of another Job
  • From a Stage to a THRON DAM PLATFORM folder (both roots and subfolders).

The final point of a Transition is called Destination.

In case the Destination of a Transition is a THRON DAM PLATFORM folder:

  • When you create a Transition, you can select the folder only among those you have access on
  • Once the asset has been published in the DAM PLATFORM folder, it disappears from WORKFLOW.

When a specific condition, called Rule, occurs, the Transition is triggered and the resource advances to the next stage of the workflow. Each phase can be linked to the others by more than one Transition. Different types of Rules can move assets to different Stages.

 

 

Rule

Rules are specific conditions that, triggering Transitions, determine the moving of an asset along the workflow.

A Rule can be represented by:

  • Anyone can move the asset – You can define that all THRON users that access WORKFLOW are enabled to apply the Rule, moving the asset by clicking the button
  • Restrict who can move the asset – You can define that only specific Users or Groups are able move the asset by clicking the button
  • Move the assets automatically – You can define the automatic application of the Rule after a certain number of likes or dislikes on an asset.
    Like and dislike is a particular kind of automatic Rule. When defining a new Transition within a Job, you can apply a Rule that automatically triggers the Transition when a certain number of users have pressed the Like or Dislike button on a specific asset.

 

 

Attachment

When you create a Job, you can attach briefs and guidelines in order to share information about the content and materials that need to be produced. You can upload any kind of file (Word, Excel, PowerPoint, pdf, etc.). Team Members can download Attachments in their original format. When the Job is deleted, attachments are deleted too.

 

 

Users and Rights

You find two kinds of users in THRON WORKFLOW: Owners and Team Members. Here below you find a description of what each kind of user can do in THRON WORKFLOW and a detailed table of users’ permissions.

  • Owners are users that can create and administrate Campaigns and Jobs. When you create a new Campaign or a new Job, you automatically become its main Owner. The main Owner can assign the rights to edit or delete Jobs and Campaigns to other team members (can be both users and groups of users), making them Owners too. Only Campaign Owners can create, edit, and remove Campaigns
  • Team Members are standard users who work on the assets of a Job but do not have the right to edit the Job itself. Team Members can be both users and groups of users, but they must already exist on the platform.

 

When you create a Job, you can define which Team Members can edit the Job and which have read-only access. These rights are valid for all the assets contained in a specific Job. Owners have full permission on Jobs.

You can see the different permissions in the table below:

Action  Owners  Team Members with edit permission  Team Members – read-only 
Create and edit a Job  X    
Add Team Members to a Job  X    
Define other Owners for a Job  X    
Upload new assets  X X  
Remove assets  X X  
Upload Job attachments  X    
Edit content information  X X  
Update assets  X X  
Download attachments in their original format  X X X
See the attachment with the name and extension in the details of the job  X X X
Define if Team Members can edit the stages of a Job or are in read-only (for all the stages of a job)  X    
Can define specific permissions for Team Members for each Stage of a job*  X    
Can comment the asset X X X

 

*Owners are enabled also to assign, for every Stage, specific permissions to Team Members who have the right to edit a Job. In particular, it is possible to define if they can:

  • download contents
  • upload a content (both create a new one or replace it with a new version)
  • edit an asset’s general information (name and description)
  • edit an asset intelligence information (tags and metadata).

Now that you know the main elements of THRON WORKFLOW, you can configurate your expansion.

Follow our step-by-step guide to know how to manage users, configurate Campaigns and Jobs, design your workflows in complete autonomy and start collaborating with your team and partners:

  1. THRON WORKFLOW – How to manage Users and Roles
  2. THRON WORKFLOW – How to create and manage your Campaigns
  3. THRON WORKFLOW – How to create and manage your Jobs
  4. THRON WORKFLOW – How to manage your workflow
  5. THRON WORKFLOW - Content life cycle within the workflow
Was this article helpful?
0 out of 0 found this helpful

Have any question?

Open a ticket
Comments