Post processing settings can be accessed from the Settings > DAM > Automations > Post processing (tab) menu.

When a post process automation task is activated, it will run automatically on each upload. If not activated, the task can be manually triggered for certain uploads via the Upload API using the postprocess parameter (e.g., postprocess=remove-background).

Post process parameters

Once a post process is selected, the user is requested to set the following parameters:

Trigger rules

When setting up a post-process, trigger rules can be specified. These rules specify conditions that must be met to activate the related task. If left empty, the task will be run on each upload.

The following variables may be used to construct rules:

Validation rules

As mentioned, the synchronous tasks provide a mechanism to validate uploads using validation rules. Possible actions when conditions have been met are:

• Refuse - The upload is rejected.

• Notice - A notice is issued, added to the file information and returned in the API response.

Availability

Please note that when marked "Unavailable", a post-process will not run and first it needs to be activated. That happens with a request to our Support Team, and in the meantime, triggering will be prevented regardless of the configuration of the post-process.

When the activation is provided and your account has enough Visual AI credits to run it, the post-process will be applied to all uploads, if the "Run on every upload" option is set to "Enabled".

Post process list

Refer to the Upload post-processes on the Automation page for a list of available post-processes.

The Workflows setting can be managed under the menu.

The Workflows feature allows you to automate complex asset management processes. It integrates internal components (such as approval flows and metadata) with external systems (like webhooks or APIs) to streamline asset validation for internal or external use.

Enable Approvals workflow

To enable Approvals:

1. Go to the Workflows section.

2. Toggle the Enable Approvals option.

This setting ensures that assets go through an approval process before moving forward in the workflow.

Accessing the Approvals Functionality

There are three ways to request an ad hoc approval, all of which lead to the new Approvals tab in the Asset Details Management modal (see below):

• Via the asset context menu: Select More actions > Manage approval
• Via the asset thumbnail: Hover over the Approval status and click Manage approval

• Via the Library sidebar (info panel): Hover over the Approval status to check the approval status (approved, pending, or rejected)

Requesting an approval

In the Approvals tab, initiate an approval request as follows:

1. Click the Request Approval button to open the Request Approval modal.

2. Complete the request by:

   • Selecting Approvers: Choose one or more approvers. Users without asset access are muted and cannot be selected. At least one approver is required to enable the Send request button.

   • Adding an Optional Message: Provide additional context for the approvers.

   • Setting a Due Date: UTC is automatically detected based on your system settings.

Once the Send Request button is clicked, all approvers receive an alert.

Managing active approval requests

Once an approval request is active, it can be modified by the original requester or anyone with the necessary permissions (if they’re not listed as an approver).

To make changes:

1. Navigate from the Summary View to the Detailed View by clicking Manage Approval.

2. In the Detailed View, you can:

   • Cancel: Cancels the request, sending notifications to all approvers (and optionally, to the requester).

   • Edit: Modify approvers, messages, or due dates. At least one approver must remain, and the due date must be in the future.

Voting on Approval Requests (Approvers Only)

Only Approvers, selected as such as part of the request, can vote and thus influence the outcome of an approval request.

An approver can have the following statuses, depending on their voting:

• Pending - hasn’t voted yet

• Didn't respond - didn't vote by the due date

• Approved

• Rejected

Approvers may add an optional message when voting to provide more context or instructions

Approver's Summary view

Approvers see a similar Summary view as the requester but with:

• The View and Approve link, leading to the Approver’s Detailed View (where they can vote and leave comments).

• No option to create a new request.

Approver's Detailed View

Approvers see options to Approve or Reject the request, with an optional comment field to clarify their decision.

Viewing Approvals as a Regular User

Regular users can view approval details but cannot take action or add comments.

Approval status display

The approval status is displayed in the following locations: 1. Asset thumbnails - top right of the thumbnail (only the status; not clickable)

2. Library sidebar - as the last field in the non-editable section of the General tab; when hovering over it, the complete summary tile is displayed; clicking on the CTA takes the user to the Summary view in the Approvals tab

1. Approval history - Clicking on this Approvals tab shows the summary tile(s) of the approval request.

The Webhooks can be accessed from the Settings > DAM > Automations > Webhooks menu.

You can add up to 5, individually configured and activated, webhooks.

Webhook parameters:

Connection

To set up the webhook, the following information must be provided:

• Hostname - The domain name of the third-party API that will be contacted.

• Path - The specific path with the Hostname forms the complete target URL (Webhook URL) to which the data will be sent.

Authentication

A consumer cannot always verify that the webhook it receives is coming from the expected source. Due to this, there are two authentication methods supported:

• Basic authentication - The simplest way to verify a webhook. It makes use of a username and a password that are used for authentication when sending the data to the Webhook URL.

• OAuth2 authentication - A more secure and complex authentication method that allows users to grant limited access to their resources without exposing their credentials. This type of authentication can be used in two ways:

  • By specifying the Authentication endpoint, username and password to retrieve a temporary token, which is then used in the webhook.

  • By directly entering the Static bearer token to use every time without generating a temporary one before the request.

Custom headers

You can specify up to 10 additional headers to be sent to the endpoint with the payload. Those headers will have the classic form name:value:

Triggers

The triggers determine the events that need to happen to execute the webhook. The following ones are available:

Asset triggers

• On upload - After a successful asset upload.

• On move - When the asset location is changed.

• On rename - When the asset is renamed.

• On delete - When the asset is deleted.

Metadata triggers

• On change meta - When some specific (or any) metadata field is modified to a value (or any).

• On change info - When some asset's information (e.g. title, description, etc.) is changed.

• On change tag - When the asset's tags are edited.

• On change label - When the asset's labels are modified.

Data to sent

There is fine-grained control over which specific asset details are sent as part of the request JSON body to the selected API endpoint. This ensures that only the necessary information to handle the event effectively is communicated. Those details are divided into several categories depending on the asset type:

* those global metadata packages to send along will include everything that is recorded for the asset in each of the 3 categories.

eg. for system metadata, it includes the file hash, labels, etc.

Note that for embedded metadata, it can be very voluminous, please only add if really necessary.

The Automation settings are accessible from Settings > DAM > Automations

Upload post-processes

Automate and enhance asset management with custom tasks triggered on asset upload. Upload post processes are actions that are triggered for a given asset upon its upload into DAM. Post-processing involves running various algorithms and ML models on an asset (e.g., detecting if it contains inappropriate content, counting the number of faces in an image, determining the dominant colours, removing the image background, and many others).

Post-process tasks are automated actions that can be performed in two modes:

• Synchronous - The results are evaluated before accepting the upload and returned in the response. The use of this mode is generally preferred in user-generated content (UGC) scenarios where user-uploaded images and videos must be moderated automatically based on several pre-defined criteria.

• Asynchronous - The results are evaluated in the background (in a non-blocking manner) after the file has been uploaded. In some cases, depending on the specified post-process type, the result will be appended to the asset's information, tags or metadata.

Post processing tasks

The following table is a summary of all available post-processing actions:

Applicable to Image Assets:

Applicable to Video assets:

Webhooks

Trigger API calls on events, automate workflows and collaborate effortlessly.

Overview

Webhooks are a powerful feature in modern web development and API integrations. They allow applications to communicate and exchange data in real-time.

They enable users to trigger API calls to third-party endpoints upon specific events and send relevant asset information.

In the context of DAM, webhooks allow users to integrate external systems, automate workflows, and stay informed about changes and, more generally, actions performed on their assets. When a relevant event takes place, such as a new file upload, file renaming, or file movement, the webhook is triggered, and a POST request is sent to a third-party endpoint, providing details about the affected asset.

Using webhooks simplifies the delivery of personalized notifications or alerts to assigned recipients whenever essential actions are executed on critical assets. This facilitates prompt responses and efficient communication.

They can also be integrated with project management tools to automatically create tasks, assign responsibilities and track progress whenever assets are uploaded to or moved within the DAM.