> 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.md).

# System Activity

**System Activity** is where administrators trace what happened in IZ Suite: who did what, which background work ran, and what an archived record looked like when it was archived. Every screen here is read-only.

Open it from **Administration** → **System Activity** 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 Activity with the System Audit Logs, Scheduler Audit Logs and Entity Archives tabs"><figcaption></figcaption></figure>

| Tab                                                                                                                                                      | What it is for                                                              |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [System Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/system-audit-logs.md)       | Every operation people and agents performed, with its request and response. |
| [Scheduler Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/scheduler-audit-logs.md) | Background work the server queued, who ran it and its log.                  |
| [Entity Archives](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/entity-archives.md)           | Snapshots of records saved when they were archived.                         |

{% hint style="warning" %}
The audit log tabs need a role that can view the system audit log; **Entity Archives** needs a role that can view entity archives.
{% endhint %}

The time-based tabs share the same tools: a time window (**Last 24 hours**, **Last 7 days**, **Last 30 days**, **Custom range**, **All retained history**), a chart of records over time where you click a bar to investigate that period, **Saved filters**, **Refresh** and **Export this page**. Filters and the selected record are kept in the page address, so you can share a link to an investigation. Times use your browser's timezone.

## Next Steps

* [System Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/system-audit-logs.md): follow an action back to its evidence.
* [Scheduler Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/system-activity/scheduler-audit-logs.md): check that background work runs.
* [Administration](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration.md): the other administration screens.


---

# 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.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.
