Audit log
An audit log records who changed a menu item, price, or table state, with a timestamp. Useful when several people share an account, and required when a manager needs to find out who marked the calamari 86 at 8 pm on Friday.
What it means in operation
Every write action in the MobiTaste dashboard produces a log entry: who, what, when, and the before-and-after values. Menu price changes, category reorders, table moves, order status flips, staff invites, settings toggles. The log is queryable by user, by date range, and by entity. Owners read it to settle disputes (“I did not raise the latte price”), and managers read it to spot training gaps (“the new hire keeps re-opening cleared tables”). The log is retained for 12 months on every plan and 36 months on Pro and Enterprise. Export is one click as CSV.
Why it matters
In a single-operator cafe the log is overkill. In any venue with two or more staff with dashboard access, it stops being overkill and starts being the only way to answer questions of fact. It is also a compliance ask in regulated markets: hotels with group IT often require an audit trail before approving a vendor. The log is also part of the security story under multi-tenant architecture, where you want evidence that the right people made the right changes inside the right restaurant.
Related terms
- Multi-tenant: the architecture that makes audit logs per-restaurant.
- Row-level security: the database-level enforcement audit logs witness.
- Organization: the account level the log belongs to.