> For the complete documentation index, see [llms.txt](https://docs.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2core.b2broker.com/back-office-guide/clients/general/history-tab.md).

# History tab

On this tab, you can view the history of changes of a client’s password, email address, verification level, and 2FA options.

Select one of the following options to view the details:

## Password change history

On this page, you can find the details about previously changed client passwords:

**Date**

The date and time when the password was changed.

***

**Type**

The type of an action that resulted in changing the password:

* **Restored** — the password was updated by a client.
* **Changed by admin** — the client’s password was updated by an administrator.

***

**Changed by**

The email address of the person who changed the password.

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

[How to change a client password](/how-to-articles/manage-clients/how-to-change-a-client-password.md)
{% endhint %}

## Test results

On this page, you can find a list of [accreditation tests](/back-office-guide/verification/client-tests.md) that a client has passed in the B2CORE UI and view their results.

## Authorization history

On this page, you can view the log of client sessions in the B2CORE UI.

**Auth date**

The date and time when a client logged in to the B2CORE UI.

***

**Auth IP**

The IP address from which a client logged in to the B2CORE UI.

***

**Auth location**

The location (country and city) from which a client logged in to the B2CORE UI, which is determined based on the client IP address.

***

**Status**

The result of a login attempt: `success` or `failed`.

## Email change history

On this tab, you can view the log of changes made to a client’s email address.

**Origin Email**

The previous client email address.

***

**Changed To**

The current email address that is used by a client to sign in to the B2CORE UI.

***

**Changed Data**

The date when an email address was changed.

***

**Changed By**

The email address of a person who changed the client email.

If an email address was specified for the first time, the **Origin email** and **Changed by** columns are empty.

## 2FA history view

The log indicating when 2FA was enabled or disabled for a client contains the following data:

**Date**

The date and time when 2FA was enabled or disabled for a client.

***

**Enabled**

The action type indicating whether 2FA was enabled or disabled.

***

**Provider**

The 2FA service provider.

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

[How to disable 2FA for a client](/how-to-articles/manage-clients/how-to-disable-2fa-for-a-client.md)
{% endhint %}

## Verification change history

On this page, you can view the details about each [verification level](/back-office-guide/verification/levels.md) obtained by a client.

This information includes the name of the previous and newly obtained levels, as well as the date and time when each verification level was obtained and the name of the person who granted the level to a client, along with a reason why it was granted.

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

[How to use the KYC constructor](/how-to-articles/manage-verification-options/how-to-use-the-kyc-constructor.md)
{% endhint %}


---

# 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:

```
GET https://docs.b2core.b2broker.com/back-office-guide/clients/general/history-tab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.