> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/reports-and-analytics/reports/app-and-systems/audit-logs.md).
# Audit logs
Find out who changed what in the Netmera panel and when: Audit Logs record user actions and configuration changes with their time and location.
**Path:** `Reports > App & Systems > Audit Logs`
Audit Logs records actions and changes inside the Netmera panel. It helps you understand who did what, when it happened, and which part of the system was involved.
Use this report when you want to answer questions such as:
* Who changed a configuration or campaign?
* When did a specific action happen?
* Which user or IP was involved?
{% hint style="info" %}
Audit Logs is especially useful for troubleshooting, security review, governance, and operational follow-up.
{% endhint %}
### Report overview
This report gives you traceability across panel activity. That includes access history, content changes, configuration updates, and other operational actions.
The main filters help you narrow the log quickly:
* **User Action** filters by the type of activity, such as login, creation, update, or feature access.
* **Log Date** places the activity in the right timeline.
### What you see in the results
The results table includes the key fields needed for investigation:
* **Date** shows when the action happened.
* **User Action** shows what type of action took place.
* **Description** adds more detail about the change or access.
* **User Name** identifies the person who performed the action.
* **User IP** helps with access tracking and security review.
### How to use this report
Use Audit Logs when something needs explanation. It is especially useful for checking an unexpected configuration change, confirming the origin of an edit, or reviewing access history for governance and security follow-up.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://user.netmera.com/netmera-user-guide/reports-and-analytics/reports/app-and-systems/audit-logs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
