# Recent activity

> For the complete documentation index, see [llms.txt](https://doc.ibexa.co/en/saas/llms.txt).

Log and monitor activity through UI and REST API.

Recent activity log displays last actions in the repository (whatever their origin is, for example, back office, REST).

![Recent activity](https://doc.ibexa.co/en/saas/administration/img/admin_panel_recent_activity.png)

To learn more about its back office usage and the actions logged by default, see [Recent activity in User Documentation](https://doc.ibexa.co/projects/userguide/en/saas/recent_activity/recent_activity/).

## Permission and security

The [`activity_log/read`](https://doc.ibexa.co/en/saas/permissions/policies/#activity-log) policy gives a role the access to the **Administration** -> **Activity list**, the dashboard's **Recent activity** block, and the user profile's **Recent activity**. It can be limited to "Only own logs" ([`ActivityLogOwner`](https://doc.ibexa.co/en/saas/permissions/limitation_reference/#activity-log-owner-limitation)).

The policy should be given to every roles having access to the back office, at least with the `ActivityLogOwner` owner limitation, to allow them to use the "Recent activity" block in the dashboard. This policy is required to view [activity log in user profile](https://doc.ibexa.co/projects/userguide/en/saas/getting_started/get_started/#view-and-edit-user-profile), if the user profile is enabled.

> **Caution: Caution**
>
> Don't assign `activity_log/read` permission to the Anonymous role, even with the owner limitation, because this role is shared among all unauthenticated users.

## REST API

You can browse activity logs with REST API. For more information, see the [REST API reference](https://doc.ibexa.co/en/saas/api/rest_api/rest_api_reference/rest_api_reference.html#tag/Activity-Log).
