Skip to main content

Home › Resources › Glossary › Audit log

Audit log

An audit log is a dated record of events in a system, showing what happened and, where captured, which account performed the action. In digital asset management, it helps teams investigate changes to files and understand how assets have been handled.

← Back to all glossary terms

A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   YZ

Page at a glance

  • Purpose: Trace recorded system activity.
  • Typical details: Time, account, action and affected item.
  • In DAM: Investigate uploads, edits and deletions.
  • Limit: A log covers only events the system records and retains.
  • Key distinction: A record of an action does not establish permission to reuse an asset.

How it works

How an audit log works

The system creates a record when a configured event occurs. An authorised reviewer can use those records to reconstruct the sequence of activity.

  1. An action occurs, such as an asset upload or edit.
  2. The system records the event and available details.
  3. A reviewer selects the relevant time period and filters.
  4. The reviewer compares the results with the issue being investigated.

Check what is logged, how long records are retained and who can access them. Missing entries do not necessarily mean nothing happened.

In practice

Audit logs in digital asset management

When a campaign file changes unexpectedly, an audit log can help a marketing team investigate the recorded activity.

Asset Bank provides an Audit Log Report covering transactions such as uploads, deletions and asset changes. Administrators can select a date range and limit results to a username or IP address. Its reporting documentation also describes separate login and usage reports.

A download record does not prove that the image was licensed for a particular campaign or show every subsequent use outside the system.

What should a marketing team check?

  • Identify the affected asset and the relevant dates.
  • Review the recorded action and account details.
  • Compare the log with approval and version records.
  • Ask the responsible person to resolve any uncertainty.

Illustrative example

Investigating a changed campaign image

Illustrative example, not a customer result. A designer notices that an approved campaign image has been replaced with an older version.

The administrator reviews the relevant dates and finds a recorded change against a colleague's account. The team checks that entry alongside the approval history and speaks to the colleague before deciding which version to restore.

Takeaway: use the log to establish the recorded sequence, then check the context. An account name alone does not explain why a change was made.

Frequently asked questions

What is the difference between an audit log and an audit trail?

An audit log records events. An audit trail is the sequence of evidence used to follow an activity or transaction, which may draw on several logs and other records.

Does an audit log prove an asset was used correctly?

No. It can show recorded activity, but permission to use a file still depends on the relevant licence, consent and approval. It may not capture use after a file leaves the system.

Does Asset Bank have an audit log?

Yes. Asset Bank documents an Audit Log Report for transactions including uploads, deletions and asset changes, with date, username and IP address filters.

Is an audit log the same as version control?

No. An audit log records activity; version control manages revisions of a file. A log entry does not necessarily include the earlier file or allow it to be restored.

See Asset Bank in action

Explore how Asset Bank helps marketing teams manage, control and share digital assets.

Keep exploring

Related terms and reading

Sources and further reading

Sources checked: 19 November 2026.