---
title: "Settings logs"
description: "Review the settings-log read boundary without exposing audit records or actors."
canonical: https://docs.ordering.co/docs/products/dashboard/settings/settings-logs/
---

# Settings logs

**Settings logs** lets level-0 administrators view audit records. Opening the page loads the newest records first; review them only when you have an authorized operational need.

> **Availability**
>
> The **Logs Audit** → **Settings logs** menu requires level 0 and an Enterprise plan. A direct link does not grant access or override your project's plan and permissions.

## Review the log table

The table can display:

- the author’s name and email;
- event type;
- configuration name/key;
- changed attribute names;
- new and old values, or added/removed values;
- date and time in the Dashboard display format; and
- the browser’s user-agent string.

![Settings logs heading and table column labels without audit records](https://docs.ordering.co/img/docs/dashboard/settings/settings-logs-overview.jpg)

The list is ordered newest first and supports page navigation. Search, filtering, export, and general record-detail controls are not available.

## View schedule changes

For a record whose changed attribute is **schedule**, **See changes** opens a comparison of the new and previous weekly schedules.

## Protect audit data

> **Sensitive audit information**
>
> Settings logs can expose staff names and emails, browser/device information, configuration names and values, option lists, schedules, and other commercial or security-relevant details. Some protected settings are masked in normal settings reads, but do not assume every value shown through the logs is redacted.

- Use masked synthetic data for screenshots, training, and support examples.
- Share the minimum needed record with authorized people only.
- Do not paste user-agent strings, real setting values, account details, schedules, secrets, or employee information into chat, tickets, or public documentation.

## What a log entry means

An entry is created when a configuration update detects changed fields. It can include the configuration, author, event, changed values, browser information, and timestamp. A missing entry does not mean that no operational change occurred; the log may not include every setting or action.

Record retention and export depend on your organization's policy. Contact your administrator if you need to confirm how long records remain available.

## Troubleshooting

### Why can’t I find a filter or search box?

The list is ordered newest first and supports page navigation. Search and filtering controls are not available.

### Why is a schedule shown as “See changes” instead of a value?

Schedules open in a comparison modal so their new and old weekly periods can be reviewed separately.

### Why is a change missing from the table?

The log can include detected field changes for configuration updates, but it may not cover every setting, action, or historical period. Use it as one source when reviewing changes, not as a complete history of all activity.

---

**Related guides:** [Language manager](https://docs.ordering.co/docs/products/dashboard/settings/language-manager/) · [Platform settings](https://docs.ordering.co/docs/products/dashboard/settings/platform-settings/)