📘



This article described the OLD version of the Audit log. This version is still active on our multi tenant instance. If you are using the single tenant or exclusive instance, please refer to the [New Audit log](🔗) article.

Audit logging offers chronological records of user activity in the Bloomreach Engagement application, including information about a user and a detailed overview of actions performed by the user. Using Audit logging provides proof of GDPR compliance and operational integrity and it can also serve as a source of information for audit investigations. Moreover, it allows you to identify the origin of any security incident.

Access to the Audit Log is restricted, and only authorized users can search, filter, or download logs for a specific time period. Audit log records will contain logs that include interaction with the application and with customer accounts.

While the Audit log is operational in all instances, access to log reports is only available in Single Tenant and Exclusive instances. If you want to use these features, contact your CSM.

🚧

Audit Log availability in BETA

This feature is currently available in the **BETA version,** but we are working on its improvement.

# Audit log at the account level

The audit log on the account level tracks all activities for a specific account. When you have several projects under one account all activities are aggregated to this audit log. Every activity is linked to the user/API who performed it. For each user/API, we track the properties described below:

The user's/API's activities trigger an `audit` event. Attributes of the audit event provide more details for the audit log:

`resource_type` describes the location/part of the application where the activity was triggered `action_type` describes the action for the `resource_type`

**Tracking activities when resource_type = customer **

**Tracking activities when resource_type = {others} ** In this case, we are talking about activities all over the application. These activities usually have among the actions either `create`, `update`, or `delete`. The resource_types provided below are just examples, much more locations are being tracked.

🚧



Data expiration time period for the audit event is set to 3 years.

# Audit log at the instance level

Tracks all activities, that don't belong to any account/project as the actions `login`/`log out`. On the instance level under the event `access`, the audit log tracks all customers who logged in/logged out.

The project for looking into the instance-level audit log is named `Audit Log - Instance`. An example of this would be `https://app.exponea.com/p/audit-log-instance1/crm/customers/pages/1`.