Audit log & notifications
Find out who did what and when, and keep low-stock and operational alerts in front of the people who can act on them.
The audit log
Dashboard → Audit Log
The audit log is the record of sensitive actions taken in your organization: who did it, what they touched, and when. It is visible to admins only.
Each entry shows
- Time — when it happened.
- User — the member who did it.
- Action — what was done, such as a refund or a completed reconciliation.
- Entity and entity ID — the exact record affected, so you can go and look at it.
Investigating something
Open Dashboard → Audit Log and filter by the kind of record you care about.
Work backwards from the time the problem appeared.
Entries are newest first; page back through them.
Use the entity ID to open the underlying order, reconciliation or stock record.
Every entry names the account that acted. Shared logins turn this trail into a single useless name.
Read this diagram as text
- Something looks wrong → Pin down when it happened
- Pin down when it happened → Filter the audit log by entity type
- Filter the audit log by entity type → An entry around that time?
- An entry around that time? → Open the record by its entity ID (yes)
- An entry around that time? → Widen the window and check related records (no)
- Widen the window and check related records → Filter the audit log by entity type
- Open the record by its entity ID → You have the member, the action and the time
Shared logins destroy the trail
The log records the account that performed an action. If three cashiers share one login, every entry names the same person and the log tells you nothing. Give everyone their own account.
Notifications
Dashboard → Notifications
Open Dashboard → Notifications.
Filter to Unread when you only want what still needs attention.
Mark one as read once you have acted, or mark all as read to clear the board.
Generate low-stock notifications to sweep the catalog on demand.
Items sitting at or below their reorder level are raised. If nothing qualifies you are told there is nothing new to report.
Alerts need thresholds
Low-stock notifications can only fire on items that carry a reorder level. Set thresholds on the lines you cannot afford to run out of — the rest are noise you will learn to ignore.
A weekly routine
Monday: clear low-stock notifications into purchase orders.
Mid-week: skim the audit log for refunds and voids.
You are looking for a pattern, not a single event.
End of week: review reconciliation variances against the same log.
A shortfall that lines up with a refund is a story worth reading.