Skip to main content

Audit Trail

How to navigate

Fynd Partners → Click Profile (upper-right corner) → Audit Trail

All the modifications that happen in your Fynd Partners account are available to you in the form of a log, also known as Audit Trail. Such a trail helps you to discover who did a particular change, where, and at what time.

Benefits​

  • It provides a clear view of how data has changed over time, enabling version tracking and rollback if necessary.
  • The audit log helps in understanding who made what changes, when, and why, ensuring transparency.
  • It offers detailed field-level tracking of changes, highlighting exactly what was modified.

Filters​

The filters ensure that you can quickly pinpoint the modification or action you’re looking for. You can use the following filters to quickly find specific logs or actions:

  • Date Range: Specify a custom date range to focus on actions that occurred within a particular timeframe.
  • Sales Channel: View the changes made within a specific website or platform linked to your business account.
  • Entity Types: Filter based on the type of entity whether it's a collection, theme, business document, subscription, domain, payout, or any other object within the system.
  • Action Type: Choose the type of action you're looking for, such as updates, delete, or new creations.
  • Entity ID: Find logs related to a particular object. Entities include collections, themes, documents, subscriptions, and more, each identified by a unique ID for easy tracking.
  • Email/Phone No: Locate actions associated with a specific email address or phone number, helping you track activity linked to individual users or sellers.

Audit Trail Table Overview​

Once the filters are applied, the Audit Trail table will display the following key information for each recorded event or action:

  • Date & Time: The date and time when the event or action took place
  • Event Details: The type of entity that was affected by the action
  • Action Type: The type of action performed on the entity. For example, Add or Update.
  • User Details: Information about the seller or user who performed the action, including their email address
  • Description: A concise description of the action taken. For example, for a brand update, the description may note specific fields such as modified_on or description that were updated.

Audit Log​

When you click on a log line item, the Audit Log Page opens, presenting detailed information about the specific event. The page is divided into several key sections for easy navigation:

Audit Details Pane​

This section provides the core event information:

  • Event: Describes the main event being tracked. For example, in this case, the event is related to a Brand Update.

    • Date & Time: The exact date and time when the event occurred.
    • ID: The unique identifier for the brand entity that was updated.
    • Action Type: The action performed, such as Update, indicating that modifications were made to the brand’s details.

  • User Details: This section includes information about the user who performed the action:

  • Device & Browser Info: Displays the device and browser used at the time of the event.

Event History Pane​

Here, you can view a timeline of events related to the entity being viewed. This allows you to track different versions or updates made over time. For example, a prior Brand Update might have occurred on August 21st, 2024, at 06:55 PM, giving you a clear picture of all modifications made to the entity.

Audit Changes Pane​

You can view the changes in two modes: Basic View and Payload View.

  • Basic View
    This tab provides a detailed view of the changes made during the selected event:

    • Path: The type of entity that was modified (e.g., Brand in this case).
    • Field: The specific fields that were changed, including the timestamp of the modification, the previous and updated values, and when the change was verified.

  • Payload View
    The Payload View displays the actual changes made between different versions of the content or configuration. Each version highlights the lines of code or text that were altered, making it easy to identify specific changes.


Was this section helpful?