> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/tools/activity-stream.md).

# Activity Stream

The Activity Stream tracks the latest actions that have occurred in the Asset Panda Pro environment and who made each change. The latest 100 changes are displayed, but you can filter the list based on a specific account, module, or collection. This allows you to audit tasks performed over time.&#x20;

The following activity views are displayed:

* [Latest changes](https://assetpanda.app/tools/latest-logs): Displays the last 100 actions that occurred in the environment.
* [Configuration logs](https://assetpanda.app/tools/config-logs): Displays the list of configuration changes in the environment.
* [Import logs](https://assetpanda.app/tools/import-logs): Display details of imports completed in the environment.&#x20;
* [Record logs](https://assetpanda.app/tools/record-logs): Displays the history of additions, deletions, and modifications to each asset record.
* [Form logs](https://assetpanda.app/tools/form-logs): Displays information on each form submission. You can click **View details** to view the records updated by the form.
* [Reservation logs](https://assetpanda.app/tools/reservation-logs): Displays information on all reservation actions (create, edit, cancel, check out/in, delete).
* [Automation logs](https://assetpanda.app/tools/automation-logs): Displays information on each time an automation was triggered, including the status of the automation and the number of records modified by the automation.
* [Offline sync log](https://assetpanda.app/tools/offline-sync-log): Displays actions with offline timestamps to help understand sync failures due to field configurations or schema changes.
* [AI logs](https://assetpanda.app/tools/ai-chat-logs): Displays information about changes processed by Ursa tasks. See [View chat logs](/ursa/ursa-administrator-tasks.md#view-chat-logs).

## Filter the Activity Stream

1. In the navigation pane, select ![Tools icon](/files/krG52m4L8n5a36jSw2oY) **Tools** > **Activity stream**.
2. Click **Filter** <i class="fa-filter">:filter:</i>. The **Filter by** page is displayed.
3. Select the **Account**, **Module**, and/or **Collection** for which you want to review changes. You can combine selections to further filter the activity stream.
4. To filter the list based on specific records:
   1. Select the **Field name** to filter the collection records.
   2. Select the **Operator** to compare the field values.
   3. Enter the **Value** to determine the records available to the collection field.
   4. To specify multiple filter criteria, click **Add more** and then repeat steps a-c.
   5. If multiple conditions are specified, select an option to determine whether **All** or **Any** of the conditions must be met to enable the record's changes to be displayed.
5. Click **Apply**.


---

# 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 dynamically by asking a question.

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

```
GET https://prohelp.assetpanda.com/tools/activity-stream.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
