> 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/my-account/my-activity.md).

# My Activity

**My activity** is the audit trail of your own account. Find an operation, isolate failures and inspect its request and response. The view only ever shows events of your signed-in user.

Open it from **Administration** → **My Account** → **My activity** in the sidebar, or from the **My activity** tab of My Account.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FI4jQCDxPDfrD6Th3yPnF%2Fv2-account-activity.png?alt=media&amp;token=27eff790-0c2e-4ac8-b0f1-bb1fe427e6f5" alt="My activity with event counts, filters, the events-over-time chart and the activity table"><figcaption><p>Your activity</p></figcaption></figure>

## Summary

| Tile                  | What it shows                                       |
| --------------------- | --------------------------------------------------- |
| **Events in scope**   | Events matching the current search and time window. |
| **Failed operations** | Recorded failures to investigate.                   |

**Export this page** downloads the events on the current page as a CSV file (timestamp, operation, actor, product, status, duration and record ID).

## Filters

| Control                              | What it does                                                                                        |
| ------------------------------------ | --------------------------------------------------------------------------------------------------- |
| **Status**                           | **All events**, **Failures** or **Successful**.                                                     |
| **Product**                          | **All products**, or one product area.                                                              |
| **Saved filters** / **Save filters** | Re-apply or save the current filters.                                                               |
| Time window                          | **Last 24 hours**, **Last 7 days**, **Last 30 days**, **Custom range** or **All retained history**. |
| **Search operation or client IP**    | Finds events by operation name or client IP address.                                                |
| **Refresh**                          | Reloads the events.                                                                                 |

**Events over time** charts matching events and failures per period. Select a bar to narrow the list to that period. Times use your browser's time zone.

## Activity Timeline

Events are listed newest first.

| Column                | Description                                                                      |
| --------------------- | -------------------------------------------------------------------------------- |
| **Event**             | The operation performed.                                                         |
| **Product / feature** | The product area and feature the operation belongs to.                           |
| **When**              | When it started, and how long ago.                                               |
| **Duration**          | How long the operation took.                                                     |
| **Status**            | **Success** or **Failed**.                                                       |
| **Client IP**         | The address the request came from, or **Not recorded**.                          |
| **Page**              | The page the action was taken from. Hidden by default; show it with **Columns**. |
| **Inspect event**     | Opens the event.                                                                 |

Use **Columns** to show or hide columns and **Export** to download the list.

## Inspect an Event

1. Click **Inspect event** on a row.
2. Read **Actor**, **Recorded at**, **Result**, **Duration**, **Client IP** and **Event identity**.
3. Switch between the **Request**, **Response** and **Variables** tabs to see what was sent and returned.
4. Click **Download this event** to save it as a JSON file.
5. Close the drawer to return to the list where you left it.

If an event has expired or is outside your access, the drawer says **Event is unavailable**.

When nothing matches, the page says **No activity matches this investigation**. Click **Reset investigation**, or widen the time window. An empty view does not mean that no activity occurred.

## Next Steps

* [Security Credentials](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account/security-credentials.md): disable a token you did not expect to see used.
* [System Audit Logs](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite-legacy/iz-core/system-audit-logs.md): the same view for every user, for administrators.
* [My Account](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/my-account.md): back to the overview.


---

# 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/my-account/my-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.
