# Events log

## List

In this subsection, you can find a list of all client-related notes and comments added on the [Event Log tab](https://docs.b2core.b2broker.com/back-office-guide/clients/general/event-log-tab) on the client details pages.

The following data is provided about each comment:

**Message ID**

The identifier of a comment in the system. Click the identifier to go to the [Event Log tab](https://github.com/b2broker-gitbook/gitbook-b2core/blob/master/back-office-guide/clients/general/event-log-tab/README.md) on the client details page. Here, you can reply to a comment or view comment threads.

***

**Tagged**

A list of Back Office users who are marked as recipients for a comment.

***

**Client ID**

The client identifier in the system.

***

**Client Email**

The client email address.

***

**Company Short**

The short name of a client’s company.

***

**Company Full**

The full name of a client’s company.

***

**Tags**

The tags assigned to a client that are used to sort the client list displayed to [Back Office users](https://docs.b2core.b2broker.com/back-office-guide/system/users).

***

**Author Admin**

The admin who added a note or comment.

***

**Message**

The text of a note or comment.

***

**Date**

The date and time when a note or comment was added.

## Categories

In this subsection, you can view and manage event log categories used to organize client-related notes and comments that are added on the [Event Log tab](https://docs.b2core.b2broker.com/back-office-guide/clients/general/event-log-tab) on the client details page.

**Category ID**

The identifier of a category in the system.

***

**Caption**

The category name.

***

**Description**

The category description.

***

**Created At**

The date and time when a category was created.

***

**Updated At**

The date and time when a category was last updated.

{% hint style="success" %}
**See also**

[How to create categories for the Event log](https://docs.b2core.b2broker.com/how-to-articles/manage-clients/how-to-create-categories-for-the-event-log)
{% endhint %}