Audit Log: Who Did What, and When

Overview

Settings → Audit log is a dated record of sensitive actions in your store: who did each one, what it touched and from which internet address. Entries are written by BestWebby as things happen; nobody can add, change or delete one from the dashboard.

The audit log is part of every plan. It is for the owner, admins and accountants. Email addresses of team members appear only to people who can manage the team.

What is recorded

Actions that change money, access or what your customers see are recorded, for example:

• refunds, team and role changes, domain changes, and exports of your data;
• product edits, one at a time, in the grid, as a bulk action, through the API or in the variants editor: a change to a product's price, compare-at price, status, stock count, reorder point, or whether stock is tracked or can be backordered is recorded with its old and new value, and so is a change to a variant's price, compare-at price or stock. Saving the whole variant list also records how many variants it added and removed;
• product CSV imports and supplier syncs, as one entry per file or sync: it counts the products whose price, compare-at price, status or stock changed and which of those fields moved, and lists the old and new values for up to 500 of those products;
• price changes made by the Clearance & Markdown Scheduler: each step, including the ones that run on their own schedule (shown with system as the actor), and the price put back when you pause or cancel a markdown, with the old and new price of the product, each storefront and each variant it changed;
• every export of your customer list or orders, with who made it and how many rows the file held;
• apps approved, registered, changed or removed, and API keys;
• customer imports that record marketing consent, with the statement you confirmed;
• custom orders turned into orders, commands run from the Operator, and approvals for products on other sales channels;
• deleted help center categories;
• every export of this log.

An entry made by BestWebby itself, rather than by a person, shows system as the actor.

Read the log

Each row shows the Time, the Action, the Actor, the Entity (the kind of record, such as order or product), the last eight characters of the record's ID and the IP address.

Click a row, or the eye icon, to open Audit detail: everything recorded with the entry, such as the old and new values or the reason given.

The list shows the newest 200 entries; click Load more for the next 200. The count next to the filters is the number of entries loaded.

Filter

• All entities — show one kind of record only.
• All actors — show what one team member did. Members who have left still show by name on their old entries.
• The two dates — from and to, both included, in UTC.

Export

Click Export CSV to download the entries that match your filters, newest first. The file has the time, action, entity, record ID, the actor's name and email address, the IP address and the details. Each export is itself recorded in the log.

One file holds up to 10,000 entries, the newest. When more entries match your filters, the page says so above the filters before you export, and the file's last line says where it stopped: "# Export stopped at 10,000 rows. Older entries are not in this file: export again with To set to" a date. Set To to that date and export again for the older entries; entries from that one day can appear in both files.

Common questions

Can I delete an entry? No. Nobody can change or delete audit entries from the dashboard.

Why is the actor's email address blank? Email addresses show only for people who can manage your team. Names show for everyone who can read the log.

Why does my export stop at 10,000 rows? That is the most one file holds. The last line of the file gives the date to export the rest from.

How do I export everything in my store, not just this log? In Settings → Danger, click Export next to Export all data. Only the store owner can do this. A smaller store's archive downloads straight away as one JSON file. A larger store's archive is built in the background: you get a notification when it is ready, and a Download button appears in the same place for 7 days. Passwords, keys and other credentials are left out. Each request, and each finished archive, is recorded in this log.