See who changed what, and when
A permanent list of the important things done in your store: settings changed, discounts given, refunds, stock moves, API keys made. Each row says when, what, on which record and by whom.
What this page is for
The audit log records important changes in your store as they happen. Rows can't be edited or deleted, so it is a trustworthy history.
Use it to answer questions like "who switched off COD?", "who gave that 20% discount?" or "did support change anything?". You need the Manage settings permission.
Find a change in 3 steps
- 1
Start from the newest
Audit log
The newest rows are at the top, 50 to a page. Use Older to go back in time and Newer to come forward.
- 2
Read the Action
Action column
The Action is a short code in capitals, like CONFIG_SET for a changed setting or POS_DISCOUNT for a counter discount.
- 3
See who did it
Actor column
Store admin is someone on your team; the code under it is their account id. Platform support is Slaby support. System is something the store did by itself, like an automatic cancel.
Common action names
- CONFIG_SET / CONFIG_RESET: a setting was changed or put back to its default.
- STORE_IDENTITY_UPDATED, BRANDING_UPDATED: store name, timezone, logo or contact details changed.
- POS_DISCOUNT, POS_RETURN: a discount or a return at the counter.
- UPI_PAYMENT_APPROVED / UPI_PAYMENT_REJECTED: a UPI-to-bank payment was checked.
- UDHAAR_PAYMENT_RECEIVED: a customer paid off udhaar.
- RETURN_APPROVED, RETURN_CREDIT_NOTE_ISSUED, RETURN_STORE_CREDIT_ISSUED: steps of an online return.
- STOCK_TRANSFER_CREATED / RECEIVED / CANCELLED: stock moved between locations.
- API_KEY_MINTED: an API key was created.
- DATA_BACKUP_EXPORTED: someone downloaded a full backup.
What the columns on this page mean
- When
- The date and time it happened.e.g. 24 Oct, 6:40 pm.
- Action
- What was done, as a short code in capitals.e.g. CONFIG_SET — a setting changed.
- Entity
- The kind of record it was done to, with that record's id under it.e.g. Order · 65f0c0ffee… — one particular order.
- Actor
- Who did it: Store admin (your team), Platform support (Slaby support) or System (automatic). The code under it is the account id.e.g. Store admin · 64ab… — compare with Team to see who.
- Reason
- The reason typed with the action, when the screen asks for one. A dash means none was asked for.e.g. "Damaged in transit" on a return.
Read next
Common questions
- How do I find who changed a setting?
- Look for CONFIG_SET rows. The Actor column shows who made the change and When shows the time.
- The Actor shows a code, not a name. How do I know who it is?
- The code is the team member's account id. Match it with the person on Team, or with Admin sessions around that time.
- Can I delete or edit a row?
- No. The log can't be changed, which is what makes it trustworthy.
- What does Platform support mean?
- Slaby support did it while helping your store. You can also see their sign-ins, marked support, on Admin sessions.
- Is every single click recorded?
- No. Important changes are: settings, discounts, returns, refunds, payments checked, stock transfers, API keys, backups and more. Plain viewing isn't.
- It says Nothing recorded yet.
- No audited action has happened in your store so far. Rows appear as soon as someone changes a setting or gives a discount.
- Who can see the audit log?
- Anyone whose role has Manage settings, usually only owners.
- Can I download the audit log?
- Not from this page. You can read it here page by page with Older and Newer.