# Audit Logs

The Audit Logs page gives administrators a complete audit trail of all changes made on the platform. Every time someone adds, updates, or removes a configuration, the action is recorded here. This makes it straightforward to trace who changed what and when, whether you are investigating an issue, reviewing access changes, or preparing for a compliance audit. Navigational actions such as viewing pages are not tracked: only actions that modify data appear in the logs.

### Filtering

Three filter buttons help you find specific events:

* **Date Range**: Defaults to the last 7 days. The exact date range is displayed above the table.
* **Action Type**: Filter by the type of change (e.g., User Locked, User Deactivated, User Reactivated).
* **Actor**: Filter by the person who made the change.

A label below the filters indicates how many filters are currently applied.

### Log Table

Each log entry contains the following information:

<table data-header-hidden><thead><tr><th width="132.33203125">Value</th><th>Description</th></tr></thead><tbody><tr><td><strong>Time</strong></td><td>When the action occurred</td></tr><tr><td><strong>Actor</strong></td><td>Who performed the action (shown as their email address)</td></tr><tr><td><strong>Action</strong></td><td>What was done (e.g., "User Reactivated", "User Locked")</td></tr><tr><td><strong>Target</strong></td><td>Which user or resource was affected</td></tr><tr><td><strong>Outcome</strong></td><td>Whether the action succeeded</td></tr></tbody></table>

### Event Detail

Clicking a log entry expands it to reveal the full context of the change, organized into four sections:

**Actor Details** identifies who performed the action, including their user ID, email, IP address, and browser user agent. This level of detail helps verify the authenticity of actions and identify the exact session involved.

**Target Details** identifies the affected resource, including its type, ID, and name.

**Changes** shows exactly what was modified, displaying the previous and new values side by side (e.g., status changed from "deactivated" to "active"). This makes it easy to understand the impact of each action at a glance.

**Request Metadata** shows the technical context, including the source (e.g., "portal") and the API path that was called.

### Pagination

Below the table, pagination controls show the total number of entries. You can configure how many entries to display per page and navigate between pages.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glbnxt.com/configure-glbnxt/platform-configuration/compliance/audit-logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.