Skip to main content

6.1 About Audit Log

Track every action for accountability, traceability, and compliance.

Updated over 7 months ago

The Audit Log provides a complete, filterable record of activity performed across the platform. Whether you’re tracking user actions, content updates, or support events, the Audit Log gives you visibility into who did what, when, and to which resource—making it an essential tool for quality assurance and regulatory traceability.


What the Audit Log Tracks

Each activity is timestamped and linked to the user who performed it.

  • Users

  • Products

  • Documents

  • Courses

  • Customers

  • Support issues


Audit Log Data Rows

The Audit Log table is structured with the following key columns:

  • UTC: The timestamp (in Coordinated Universal Time) for when the action occurred

  • Resource Name: The name of the item (e.g. course, product, etc.) that was affected

  • Resource ID: The system ID of the affected item (clickable for quick access)

  • Type: The content type (e.g., Course, Document, User)

  • Action: Indicates if the item was Created, Updated, or Deleted

  • Performed By: The user who made the change

  • Changes: A detailed description of what was modified (e.g., version number, object state)


Filters and Controls

Filter the audit log by content type using the toggles for:

  • Users

  • Products

  • Documents

  • Courses

  • Customers

  • Support

These let you instantly narrow down the log to specific areas of interest.


Date Filter & Export

Use the From and To date pickers to narrow results to a specific time range. Once filtered, you can click Download CSV to export the results for compliance reporting, backups, or internal audits.


Inline Column Filters

Each column has its own text or dropdown filter, allowing precise filtering based on resource name, ID, action type, performer, or change details.


Use Cases

  • Regulatory compliance: Export logs for audit trails or inspections

  • Internal QA: See exactly when and how a course or document was modified

  • Collaboration transparency: Know which team member published or updated what

  • Rollback decisions: Understand version histories and state changes in detail

Did this answer your question?