Skip to content
  • There are no suggestions because the search field is empty.

Audit logs

The Audit Logs page provides a detailed and traceable record of user activity across Vince Live. It is essential for monitoring changes, ensuring accountability, and maintaining data governance.

Key Features

1. Entity Filter

  • Dropdown to select a specific entity type (e.g., workflow, table).
  • Helps narrow results to relevant categories.

2. Date Range Selection

  • Start Date and End Date filters allow for time-based audit review.
  • Useful for compliance reporting and investigation.

3. Search and Apply

  • Search bar to filter by keywords (user, action, etc.).
  • Apply button to activate filters.
  • Reset restores the default unfiltered view.

🔹 Audit Log Table Columns

Column Description
User Name Identifies the user who performed the action
Timestamp Date and time of the change
Entity Type of object affected (e.g., workflow)
Name The specific name of the item modified or deleted
Action Indicates the type of action: Updated, Deleted, etc.
Details Describes what was changed (e.g., updated tags, properties, definitions)

🔹 Row Expansion

Clicking the arrow beside a row reveals:

  • User: Full user name
  • Date Modified
  • Change Summary
  • "View Changes" button: opens a detailed diff of the update

🔹 Detailed Change View (View Changes)

Displays a precise comparison between the old and new versions of the changed entity:

  • Sections: Grouped by change areas (e.g., overview, definition, modified)
  • Color-coded Diff:
    • Red = removed/previous content
    • Green = added/updated content

Example Changes:

  • Added a new block to the workflow with:

    json
    CopyEdit
    {
    "stepId": "table_1",
    "name": "Table",
    "type": "TABLE",
    "target": "workflow-custom-table"
    }

  • Updated timestamps in modified section.


🔹 Use Cases

  • Compliance auditing: Review who made what changes and when.
  • Error tracing: Identify unintended modifications.
  • User accountability: Monitor admin and developer activity.

Best Practices

  • Apply filters to avoid data overload during investigations.
  • Use View Changes for version comparison and rollback validation.
  • Regularly review logs for unauthorized or unexpected modifications.