Skip to content
ForkLine Docs

Activity Log

Admin → Activity records who did what in your restaurant. It's available to Owners and Managers.

What's recorded

Actions that change money, access, or configuration:

  • Menu changes — prices, availability, items added or removed
  • Settings changes — hours, ordering, payments
  • Order actions — cancellations, refunds, status overrides
  • Register actionsdiscounts and their reasons, custom items, cash payments, reader charges, no-sale drawer opens
  • User changes — invites, role changes, removals
  • Register account lockouts — see below

Each entry records who, what, and when.

Register accounts show up here too

If you use register accounts, entries record the cashier in addition to the device's account.

The tablet's account is still the authenticated user, so an entry reads like "Maria (on the counter iPad's account)" — you get both the person and the device. You can search by cashier name.

This is the thing the log could never answer before: which human was standing at the counter.

Sign-ins and sign-outs aren't logged. They happen many times a shift and the attribution is already on everything those people then do.

Lockouts are logged, explicitly. The log otherwise records only successful actions, and a lockout is by definition a failure — exactly the thing worth seeing.

Searching

Search and filter to answer a specific question. Search runs across the whole log server-side, not just the page on screen, so an entry from months ago is findable.

Useful questions to bring to it:

  • "Who changed the price of this item?"
  • "Who refunded that order?"
  • "How many discounts did we give on Saturday, and why?"
  • "Who opened the drawer with no sale?"

Passcodes are never stored in the log

Register passcodes are filtered out of log entries. An audit record holding a PIN in clear text would defeat the point of hashing it.

Using it well

Review discounts periodically. Discounts require a reason, which makes them worth reading. A pattern of large discounts at one time of day is worth understanding.

Check it after an unexpected change. "The price is wrong and nobody knows why" is exactly what this is for.

Don't use it as a surveillance tool. It's an audit trail for investigating specific questions. Staff who feel watched by default behave worse, not better.

Where to go next

Last updated · View as Markdown