# How to view the settings change log?

The settings change log shows who changed critical platform parameters and when — topics, roles, client fields, sender emails, and other entities. Use it to quickly trace an unexpected configuration change during an incident investigation.

## When you need this

- You need to find out who changed a role, topic, or other setting.
- After an incident, you need a timeline of configuration changes.
- You want to verify whether critical settings were modified during a specific period.

## What to know

- **The feature is off by default** — a root administrator enables it in **Instance settings** (category **System**, toggle **Settings Audit Trail**).
- **Menu item** — only **root administrators** see **Settings change log** in the sidebar. If the feature is off, the page shows a message that the log is disabled.
- **Other roles** — if an administrator granted view permission, open **`/settings-page/settings-audit`** directly in the browser (the menu item may be hidden).
- **Retention** — the system automatically removes old records (typically around 180 days).

## Before you start

- [x] You are signed in as a root administrator or a user with permission to view the log.
- [x] A root administrator has enabled **Settings Audit Trail** in instance settings.

## Step-by-step

### 1. Enable the log (root administrator only)

1. Open **Settings** (`/settings-page`).
2. In the sidebar, open **Instance settings**.
3. Scroll to the feature toggles block and expand the **System** category.
4. Turn on **Settings Audit Trail**.
5. Refresh the log page if it was already open.

For more on instance settings, see [How to configure instance parameters](/en/settings/how-to/configure-instance.md).

### 2. Open the settings change log

**If you are a root administrator:**

1. Open **Settings** (`/settings-page`).
2. In the sidebar, expand **Technical Diagnostics**.
3. Select **Settings change log**.
4. A table with recent changes opens.

**If you have view permission but are not root:**

1. Sign in with an account that has the appropriate role.
2. Open **`/settings-page/settings-audit`** in the browser.

### 3. Review entries

Each row shows:

- **Time** — when the action occurred.
- **Actor** — who made the change.
- **Module** — where the entity lives (for example, operator panel, settings, Fast Line Pro).
- **Entity** — what was changed (topic, role, tag, and so on).
- **Action** — create, update, or delete.
- **Summary** — a short description of the change.

### 4. View change details

1. Expand a row in the table (click the row).
2. In **Field changes**, see a table with field / before / after values.
3. If a detailed field list is unavailable, the page shows **No detailed diff** or a similar message.

### 5. Filter entries

1. Set a **date range**.
2. Choose **module**, **entity type**, **action**, or **actor** from the dropdowns.
3. Type in the **search** field to find entries by name or summary.
4. Click **Refresh** to reload data manually.

### 6. Grant access to another role (optional)

1. Open **Settings** → **Roles**.
2. Open the role that needs access to the log.
3. Enable the permission to view the settings change log (if available in the permissions list).
4. Save the role.

## What happens next

- You see a timeline of critical setting changes linked to a user and timestamp.
- New changes to supported entities appear automatically while the feature is enabled.

## How to verify it worked

- After enabling the feature, the page shows a table of entries instead of a disabled-log message.
- Make a test change (for example, create a topic) and confirm a new entry with action **Create** appears.
- Expand the entry and confirm the **Field changes** block shows **field / before / after** columns.
- Confirm filters narrow the list to the expected entries.

## Related materials

- [Configure instance parameters](/en/settings/how-to/configure-instance.md)
- [Configure roles](/en/settings/how-to/configure-roles.md)
- [View system status](/en/settings/how-to/view-system-status.md)

## Important notes

- ⏳ **Without enabling the feature**, changes are not recorded — turn on **Settings Audit Trail** in instance settings first.
- 📋 **What is logged:** topics, tags, roles, bots, client fields, sender emails, custom modules, Fast Line Pro agents and knowledge bases, Action Jail, QA checklists, files, broadcast templates, and other critical operator panel entities.