> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Viewing Settings History

> Audit every change applied to Bank Transfer settings.

The **History** tab on the Settings page lists every change applied to the plugin configuration, in chronological order. Use it to answer questions like *who changed the daily limit last week?* or *when did we flip the webhook on?* without digging through logs.

## Accessing the history

***

<Steps>
  <Step title="Open Settings">
    In the Bank Transfer sidebar, click **Settings**.
  </Step>

  <Step title="Switch to the History tab">
    At the top of the page, click the **History** tab.
  </Step>
</Steps>

## Columns

***

Each row corresponds to a single field change.

| Column    | Description                                                                                                                                      |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Timestamp | Date and time of the change (format `YYYY-MM-DD HH:mm:ss`).                                                                                      |
| Key       | The setting key that changed, in dotted notation (for example `usage_limits.daily_limit_cents`, `webhook.enabled`, `operating_hours.open_time`). |
| Old Value | The value before the change.                                                                                                                     |
| New Value | The value after the change.                                                                                                                      |
| Actor     | The identifier of the user or service that made the change.                                                                                      |
| Revision  | Monotonically increasing revision number assigned at save time, shown as a badge.                                                                |

## Reading secrets

***

Secret fields (password, private key, webhook signing secret) are never stored in clear text in the history. When a secret is changed, both **Old Value** and **New Value** show `••••` so the fact of the change is auditable without exposing the secret itself.

## Empty state

***

If no changes have been recorded yet, the tab shows *No changes recorded yet*. The first save on the Settings tab populates the history.

## How entries are created

***

Every time you click **Save** on the Settings tab:

1. The plugin compares the form values against the last saved state.
2. It sends only the fields that changed.
3. Each changed field becomes a separate entry in the history, sharing the same revision number.

This means a single save that updates three fields produces three rows, all stamped with the same revision — so you can see which changes were grouped together.

## Tips

***

* Keep the History tab handy when investigating issues. A regression that started at a specific time often lines up with a setting change visible here.
* When coordinating a change with a third party (for example a new JD environment), note the revision number — it is a stable reference to the exact configuration live at that moment.