Event logs

What this feature is for

The Event logs give you a trustworthy history of what happened in the active restaurant: who changed what, and when. The log is append-only, so entries are never edited or deleted, which makes it a reliable record for reviewing activity and undoing a mistake.

Who can use it

Owners and Admins can open the Event logs and, where an entry supports it, revert a change. Staff and Viewers do not have access to the logs.

Availability and required module/permission

The Event logs are part of the core platform and need no purchasable module. Viewing the logs requires the view permission, and reverting an entry requires the revert permission; both are limited to Owner and Admin.

Prerequisites

None. The Event logs are available as soon as your account has a restaurant and record events as they happen.

Common tasks

Review recent activity: open the logs to see the latest changes for the restaurant.
Revert a supported change: open an entry that can be undone and revert it.
Trace a change: find who made a change and when it happened.

Screen and field reference

Each entry describes one event with its actor and time. Entries that can be safely undone offer a revert action; entries that only record what happened do not. Reverting itself is recorded as a new event, so the history stays complete.

Warnings and important constraints

The log is append-only and cannot be edited or cleared. Personal information such as guest names, email addresses, and phone numbers is redacted in the logs to protect guest privacy.

Troubleshooting guidance

If an entry has no revert action, that change is not reversible from the logs. If you expected an event and do not see it, confirm you are looking at the correct active restaurant.