Skip to content
Help

Activity log

The audit trail — who changed what, when, and from where.

Team & operations2 min read

Settings → Activity. Every meaningful change in Restro is written to an immutable log.

#What each entry records

  • Entity — what was touched: an order, a menu item, a customer, a shift, a branch.
  • Action — created, updated, deleted, cancelled, completed, paid, refunded, opened, closed, and so on.
  • Actor — who did it: a staff member, a customer, the system, an API key, or an inbound webhook.
  • Approver — the manager who authorised it, when the action needed approval.
  • Source — where from: dashboard, POS, cashier app, kitchen, waiter app, driver app, website, mobile app, API, webhook, or system.
  • Terminal — the paired device the action came from, for anything done in a staff app.
  • Changes — the specific fields that moved, with their before and after values.
  • When — the timestamp.

#Work done on a terminal

Once a device is paired and a staff member has signed in with their PIN, everything they do on it is attributed to them personally — orders rung up, tips, cash movements, refunds and voids. The entry names the person, the terminal, and which app it came from, so a shared till still produces per-person accountability.

#Manager approvals

Some actions are held behind a manager's PIN — closing a drawer with a large variance, or voiding and refunding when the signed-in member lacks the permission. These entries record both people: the member who performed the action and the manager who approved it. An approval never hides who actually did the work.

Both names are searchable, and a manager's profile shows the approvals they granted alongside their own work.

#Filtering

Filter by entity type, by actor, by source, by branch, and by date range. To answer who voided that order, filter to orders and the cancelled action on the day in question. To review everything that happened on the tills, filter the source to the point of sale.

#API and webhook activity

Actions taken through the public API are logged with an API actor and the name of the key that made them, so an integration misbehaving is as traceable as a person doing the same thing.

Did this page miss something? Tell us.

Back to top