The audit log is restricted to account owners and admins. Staff on other roles will see a “restricted” message when they try to open it, and an admin whose access is limited to particular stores only sees events for those stores.
Where to find it
1
Open Logs
In the sidebar, click Analytics to expand the section, then select Logs.
2
Open the Audit Log
Under the Security heading, select Audit Log.
3
Search and filter
The most recent events load automatically. Narrow the results with filters, or export what you see to CSV.
What gets recorded
Each entry captures the full context of a single staff action:
Selecting a row expands a detail panel with the request method, path, route, IP address, user agent, request ID, and trace ID, along with the error type when an action failed.
Which actions are logged
- All changes are recorded — anything that creates, updates, or deletes data (including actions like archiving, cancelling, restoring, or publishing).
- Sensitive reads are recorded — viewing or downloading reports, exports, invoices, and statements. Opening the audit log itself is recorded as a
read, and exporting it is recorded as anexport. - Routine reads (browsing lists, opening detail views, background polling) are not recorded, to keep the log focused on meaningful activity.
Actions taken by customers placing orders and by API keys are outside the scope of the audit log — it focuses on staff actions in the dashboard.
Who Changed a Store Setting, and When
Saving a store settings page is recorded like any other change: anupdate against the resource behind that page, attributed to the staff member who saved it and stamped with the time they did.
Opening hours are the common case. Weekly hours and Special Opening Hours are saved together by Save on Stores → your store → Settings → Opening Hours, so both arrive as one entry with resource type hour and action Update.
1
Filter to hours changes
Click Add filter, choose Resource type, enter
hour and click Apply. Add the Action filter set to Update, and the Outcome filter set to Success — failed saves are logged too, and they did not change anything.2
Set the date range
The log opens on the last 30 days. To narrow it, click the date range button with the calendar icon to the right of the filters and pick a preset (Today, Yesterday, This month, Last month, This year, Last year, All time) or select the dates on the calendar. All time will not surface anything beyond your retention window.
3
Read the row
Time is when the hours were saved, Actor is the staff member who saved them (name, email, and their role at the time), and Store is the store affected — so you can leave the Store filter off and read the column instead of looking up store IDs.
4
Expand it for the request detail
Selecting the row shows Path as
/venues/<store id>/hours, the IP address, User agent and Request ID, and Fields changed as venueHours and specialHours.venue for a store’s own settings, and menu, product or discount-code for catalogue and promotion edits) and read the Actor and Time columns.
What this does not tell you
- The values. The log records that hours were changed and which fields were involved — never the times before and after. There is no way to see the previous opening hours in the dashboard.
- Changes that were not made by a staff member. Anything done by an API key, a POS or delivery integration, or a customer is out of scope.
- Anything older than your retention window. 30 days by default (see Retention).
If a change is older than your retention window, or was made by an integration, the audit log cannot tell you who made it. Contact support with the store and approximate date if you still need it investigated.
Searching and filtering
The audit log uses a faceted search bar. Add one or more filters and click Apply; active filters appear as removable pills. Available facets:
By default the log shows the last 30 days. Results are paginated — use Load more to fetch older events. You can clear everything with Clear all.
Exporting to CSV
Click Export to download the currently filtered results as a CSV file (with the same filters and date range applied). This is handy for sharing with auditors or archiving outside storekit.Exports are capped at 50,000 rows. If you hit the cap, narrow the date range or add filters and export in smaller batches.
Privacy and data handling
The audit log is designed to record what changed without capturing sensitive contents:- It stores the names of the fields involved in a change (e.g. “price, availability”) — never the actual values that were submitted.
- Field names that look sensitive (passwords, tokens, keys, card details, PINs, and similar) are automatically dropped and never recorded.
- Records are append-only: entries are never edited or individually deleted, so the history stays trustworthy.
Retention
Audit entries are retained for 30 days by default, and the log opens on that same 30-day window. Retention is set per account, so accounts that need a longer history for compliance can request one.Who can see the audit log?
Who can see the audit log?
Only account owners and admins. Other staff roles cannot view or export it.
Why don't I see routine page views?
Why don't I see routine page views?
The log intentionally records changes and sensitive reads (reports, exports, invoices, statements) only. Everyday browsing and background requests are excluded so the log stays focused on meaningful activity.
Does the log store the data I changed?
Does the log store the data I changed?
No. It records which fields were involved in a change, but not the submitted values. Sensitive field names are dropped entirely.
How far back can I look?
How far back can I look?
Entries are kept for 30 days by default. If you need longer retention for compliance, contact our team.
Can I export the whole log?
Can I export the whole log?
You can export the filtered results, up to 50,000 rows per export. For larger ranges, split the export into smaller date windows.