> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/system-audit-logs.md).

# System Audit Logs

**System Audit Logs** records every operation performed in IZ Suite, by people and by agents. Use it to follow an action back to its evidence: find the operation or actor, isolate failures and inspect the exact request and response.

Open it from **Administration** → **System Activity** → **System Audit Logs** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkJSNgiR1NrUDKNUEN9Va%2Fv2-audit-system.png?alt=media&amp;token=61456d9e-cfd1-47c3-bb3c-faba6804ab48" alt="System Audit Logs with event counts, filters, time window and the events-over-time chart"><figcaption><p>System Audit Logs</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view the system audit log. To see only your own activity, use **My Activity** under **My Account**.
{% endhint %}

## Counts and Filters

| Tile                  | Description                                                    |
| --------------------- | -------------------------------------------------------------- |
| **Events in scope**   | Events matching the current search and time window.            |
| **Failed operations** | Recorded failures to investigate. Click to list only failures. |

| Filter                                         | Description                                                                                                   |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Status**                                     | **All events**, **Failures** or **Successful**.                                                               |
| **Product**                                    | The product area the operation belongs to.                                                                    |
| **People**                                     | One or more people.                                                                                           |
| **Actor type**                                 | **People** or **Agents**.                                                                                     |
| **Search operation, user, agent or client IP** | Free-text search.                                                                                             |
| Time window                                    | **Last 24 hours**, **Last 7 days** (default), **Last 30 days**, **Custom range** or **All retained history**. |

**Events over time** charts matching and failed records per period. Click a bar to investigate that period. **Saved filters** and **Save filters** keep a filter combination.

## Activity Timeline

Newest events first. Failed events are highlighted.

| Column                | Description                                                                        |
| --------------------- | ---------------------------------------------------------------------------------- |
| **Event**             | The operation, for example "Save suite ai access rule". Click to inspect it.       |
| **Actor**             | The person, or the agent marked "(agent)".                                         |
| **Product / feature** | The product area and feature.                                                      |
| **When**              | When the operation started.                                                        |
| **Duration**          | How long it took, in milliseconds.                                                 |
| **Status**            | **Success** or **Failed**.                                                         |
| **Client IP**         | The address the request came from.                                                 |
| **Page**              | Hidden by default. The screen the action was taken from. Show it with **Columns**. |

**Export this page** downloads the events on the current page as CSV.

## Inspect an Event

1. Click the event name (or **Inspect event** at the end of the row).
2. Review **Actor**, **Recorded at**, **Result**, **Duration**, **Client IP** and **Event identity**.
3. Open the **Request**, **Response** or **Variables** tab to see what was sent and returned.
4. Click **Download this event** to save it as a JSON file.

The panel keeps your place in the list. If an event is no longer available, it may have been removed by your retention policy.

{% hint style="info" %}
Audit logs are kept for the retention period set in the archival policies under global settings; older records are archived. Certain field values in requests may be masked based on their sensitivity.
{% endhint %}

## Next Steps

* [Scheduler Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/scheduler-audit-logs.md): trace background work the server ran.
* [Entity Archives](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/entity-archives.md): see what an archived record looked like.
* [System Activity](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity.md): the other tabs.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/system-audit-logs.md?ask=<question>&goal=<user_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.
