> For the complete documentation index, see [llms.txt](https://docs.udara360.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udara360.io/core-features/operations/audit-trail.md).

# Audit Trail

The Audit Trail page gives you a complete log of user and system activity across Udara360, covering logins, updates, creations, and deletions. Use this page to trace who did what, when, and from where, for security and compliance purposes. This guide will walk you through accessing, viewing, and filtering audit log entries.

## Accessing Audit Trail

1. Log into the application using your credentials.
2. From the dashboard, navigate to **Operations** in the side menu.
3. Expand **Operations** and Select **Audit Trail** from the dropdown list.

<figure><img src="/files/1MpAJRtt79XXNkXnC3I6" alt=""><figcaption></figcaption></figure>

### **Features of the Audit Trail Page**

#### **Viewing Audit Logs**

The audit logs display various addresses, showcasing user actions, subjects, operation types, and relevant identifiers. Users can use the Filter button to find specific actions based on criteria such as function, initiator, or date range to facilitate searching. Additionally, the Reset Filter button is available to clear any active filters and restore the complete list of audit logs. Each entry includes a serial number (S/N) for reference.

#### **Filtering and Searching**

The Filter button allows you to search for specific actions based on function, initiator, or date range criteria. Click the Reset Filter button to clear any active filters and restore the complete list of audit logs.

#### **Audit Trail Details List:**

* **S/N:** A serial number for reference.
* **Initiator ID:** The email address or identifier of the user who acted.
* **Full Name:** The full name of the initiator.
* **Subject Name:** The name of the subject involved in the action (e.g., “User,” “Communication Template”).
* **Function:** The specific action performed (e.g., “Login,” “Update Customer Information”).
* **Operation Type:** The type of operation (e.g., “Update”).
* **Subject Identifier:** A unique identifier for the subject (e.g., an email or account ID).
* **Creation Date:** The date and time when the action was logged.
* **Initiator IP:** The IP address from which the action was performed.
* **Actions:** Provides an option to view more details for each log entry.

#### **Reviewing Log Details**

To access a detailed view of each log entry, click the view icon (eye symbol) in the Actions column. This detailed view allows administrators to evaluate the context and specifics of an action for a comprehensive understanding.
