Viewing Settings History

Audit every Bank Transfer setting change in Lerian Console — timestamp, key, old and new value, actor, and revision number for compliance reviews.

The History tab on the Settings page lists every change to the plugin configuration in chronological order. Use it to answer questions such as who changed the daily limit last week? You do not have to search the logs.

Accessing the history

---

1. Open Settings

   In the Bank Transfer sidebar, click Settings.

2. Switch to the History tab

   At the top of the page, click the History tab.

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.timeout_ms, 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

---

The history never stores a secret field in clear text. Secret fields include the password, the private key, and the webhook signing secret. When you change a secret, both Old Value and New Value show ••••. This keeps the change auditable and does not expose the secret.

Empty state

---

Before you record any change, the tab shows No changes recorded yet. The first save on the Settings tab creates the first entry.

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 with the same revision number.

So a single save that changes three fields produces three rows. The three rows share one revision number. You can see which changes went together.

Tips

---

• Keep the History tab open when you investigate an issue. A regression often lines up with a setting change that you see here.
• When you coordinate a change with a third party (for example, a new JD environment), note the revision number. The revision number is a stable reference to the exact configuration live at that moment.