Asset history log

Basic asset history

Asset history and general information are listed beneath the preview of the asset when you first open the asset module. Here, you can find:

• The date the asset was created.
• The user who created the asset.
• The date the asset was last updated.
• Brandfolder shows the date when the asset publishes (if asset availability is enabled).
• The date the asset expired (if asset availability is enabled).
• The user who approved the asset (if approvals are enabled).

Access the asset history log

Users can access the asset history log in two ways: 

1. Select View recent updates in the asset module.

   Brandfolder Image

   
2. Navigate to the asset modal > Workflow > Asset > Asset history.

Brandfolder Image

Information shown in the asset history log

This log provides updates on individual assets only. Changes made at the Organization or Brandfolder level aren't included here.

Some examples of updates include changing asset data such as tags, descriptions, custom field values, and comments, updating a version, adding an attachment, adding an individual asset watermark, and more. 

The log is displayed chronologically and contains up to 180 days of data. After 180 days, the data is unavailable.

The asset history log clearly differentiates between the creation and deletion of an asset or an attachment. However, for other updates, such as tags, comments, descriptions, and more, the log doesn’t specify whether an update was a creation, edit, or deletion. For instance, if an update indicates tags, it means a tag was created, deleted, or edited on the asset.

There are five columns of information contained in the log: 

• Update: The generic update that occurs to the asset.
  • Examples: Tags, Description, Comment, Section, and Collections.
• Source: The agent or method that made the update.

  • Example: Brandfolder UI, CSV Metasheets, Auto-Tagging, and Asset Automations.

    If an update comes from a third-party integration without a source field, APIv4 displays as a placeholder.

• User: The actor, person, or system that started the change.

  • Example: A user's email.

    If the update was made from an agent with unavailable information, such as a third-party integration or automation, the user information displays as a hyphen “-”. This is expected and intended behavior.

• Date: The date the update took place.
• Time: The time at which the update took place.