A product drops off the Online Store channel on a Tuesday morning, and nobody in merchandising scheduled the hide.
Support can still see the listing and the ads still point at it, so the question on the team call is narrower than a security scare. Someone, or some app, changed availability, and the store needs a named owner for that kind of edit before it happens again.
Shopify rebuilt the Store activity log for that question. The 13 November 2026 changelog says the new log answers "who changed what, and when?" without digging through different pages.
Introduction
Think of the new log as the visitors' book at a reception desk. Each row records who signed in, what they touched and when, but some visitors sign with a company name and a few leave the line blank. This post shows how to read that book for product, theme, and app-access changes, then fill in what we call the owner sheet: one row per change type, with the person who answers for it. Counting the extra clicks that the 2026 admin redesign added to search and notifications is a separate task, covered in Shopify Admin Redesign: Count the Daily Tasks That Gained Clicks.
The rebuild shows where Shopify is taking the admin, with the live store treated as a change record that has an actor column, and the merchant deciding who may write each resource. The record is still partial. Shopify Help and the changelog both say history starts from when each change type began being recorded, that not every admin action is recorded yet, and that some changes made through apps carry no person's name.
Product, theme, and app-access changes go on the owner sheet first, because they alter what buyers see or which apps may write to the store. A weekly filter on those three catches an unexplained edit while the people involved still remember the week.
What merchants are reacting to
Merchants already treat unexplained admin edits as a trust problem. A collection vanishes, a theme looks different from last week's publish, or an app that nobody remembers approving still has access.
The older log made that hunt hard. Shopify Help documents the current version as a view-only list that displays a maximum of 250 results, with no export and no way to show actions over a set number of days. On a busy store those 250 rows go quickly, so the person who unpublished a product last month may already have dropped off the bottom of the list.
The rebuilt log answers with filters for Actor, Resource type, Resource, Action, Changed field, and Date range. Select a row and the details show what changed, including previous and new values where Shopify has them.
The table will still leave some "who did this" arguments open, because it keeps returning app names, Shopify as the actor, and Actor unavailable. The owner sheet closes them by saying who owns product availability, who owns theme publishes, and who owns app access.
Confirm which Store activity log you have
Open Settings, then General, then Store activity log. Shopify Help says both versions open from that same place on the Settings page while the rollout is in progress.
Check your own screen, because access depends on role and a colleague's view of the same store may differ. The current log is a list you cannot click or filter. The new log is a table with filters such as Actor and Date range, and each row opens for details.
Shopify Help gives the new table to store owners, organization owners, and staff with the Administrator or Organization administrator role once it is available to them. Some other staff who can manage users and who also have Store settings, then Manage settings, also get the new table. Everyone else with Home and Manage settings stays on the current list, and saved links to the current log open the new one for anyone who has it.
The 13 November 2026 changelog says the new log is available to store owners and to staff with both the Manage settings and Edit permissions staff permissions, such as the Administrator and Organization administrator roles. If the merchandiser who unpublished the product cannot open the table, give the weekly review to someone who can and bring the merchandiser onto the call.
You can ask Sidekick to open the store activity log, and Shopify Help says Sidekick cannot answer questions about the entries in it. Use Sidekick to reach the page, then read the rows yourself.
Filter product, theme, and app-access changes by actor
Start with the three change types that alter the live storefront or the apps allowed to write to it.
The changelog lists products, orders, discounts, themes, apps, staff, payments, and store settings in the rebuilt log. Pages across admin, including products, orders, discounts, gift cards, collections, and domains, also include a View activity action that opens the log already filtered to that item. Use View activity when you already know the resource, and the full log when you are still looking for it.
For an unexplained hide, open View activity on the product, or filter Resource type to products, then set a date range back to the last time anyone saw it on the storefront. Add the Actor filter once you have the rows. The first pass asks what changed, and the second pass asks who Shopify recorded as the actor.
For a theme surprise, filter Resource type to themes and open each row that does not match a planned release. Shopify Help says theme actions can show Online Store as the actor when someone worked in the theme editor or through the Online Store channel, so the row names the channel and leaves out the person. That is why the owner column on the sheet sometimes holds a permission in place of a name. Theme assignment during an Experiment is a different problem, covered in Shopify Theme Rollouts: Confirm This Before You Replace, so keep rollout flags off this sheet.
For app access, narrow Resource type to app changes. Shopify Help lists granting store access to an app among its own examples of store activity, so access grants are the rows to read first. The invoice and duplicate-fee audit belongs to The Hidden Cost of Running a Shopify Store When 12 Apps Quietly Eat Your Margins, and this filter only asks who granted access that is still live.
A health and wellness stack like YuMOVE shows why the actor column matters. oContis supported YuMOVE through a Recharge-to-Ordergroove migration of more than 300,000 customers, built custom Gadget apps as middleware for customer support, and helped build a custom quiz alongside YuMOVE's in-house developers. When several teams and apps write to one store, the weekly review is how you later separate a support-app write from a merchandiser's edit without guessing.
Read actors that are not a named staff member
Named staff are the easy rows, and the real work sits in the other labels.
In the new log, Shopify as the actor means Shopify staff made the change, for example through Shopify Support. Match those rows to a Support ticket before you treat them as unknown. The current log used the same label more loosely, including for background jobs that process bulk edits, so an old reading of Shopify as the actor does not carry over to the new table.
Some changes have no recorded actor, often bulk updates from apps, and Shopify Help describes two ways they appear. A change made through an app shows Via followed by the app name in the Actor column, with Actor unavailable and the app name in the details. In visitors' book terms, the courier signed with the firm's name, and Shopify adds that the app name shows how the change was made, which may differ from who made it. Other changes show a dash, with Actor unavailable in the details, which is the blank line in the book.
To review both kinds as a set, filter Actor to Actor unavailable. A filter for one specific app includes only changes where that app is the recorded actor, so its Via rows stay out of that app's filter and turn up under Actor unavailable instead.
That gap matters on a beauty and skincare launch such as Filter by Molly-Mae, where oContis shipped the Shopify theme and the listed project partners include Klaviyo and Yotpo. Rows from apps like these can arrive with the app as the actor or as Via the app, and in both cases the owner on your sheet is the person allowed to keep that app installed.
Connectors that can write admin data belong on the same owner list. Production isolation for the Claude connector is its own job, covered in Shopify Claude Connector App: Setup, Permissions, and Risks. Once it is installed, its writes should show up as an app actor, which is why the app-access and product filters stay on the weekly pass.
Some changes are recorded in other places, and Shopify Help names an order's Timeline and the user management activity log as examples. Orders, customers, and inventory transfers keep their own Timeline, staff and role changes sit in the user management activity log, and POS voids and manual discounts sit in the POS activity log. The Store activity log is the store-wide table, and those records stay where they are.
Assign an owner for each unnamed live change type
Build the owner sheet with one row per live change type you care about this week. Start with product availability, theme publish, and app-access grants, and add payments and store settings only after those three have owners.
For each row, record the resource, the filter you used, the actors Shopify returned, and the person who may approve a repeat. If a named staff member made the change, the owner is that person together with their manager. If the actor is an app, Via an app, or Actor unavailable tied to an app name, the owner is whoever is allowed to keep that app installed. If the actor is Shopify, the owner is whoever opened the Support request, and if the actor is Online Store, the owner is whoever holds theme editor access.
Shopify Help says you can filter entries, and that you cannot search them by keyword or export them. That makes the owner sheet your export, and eighteen months of retention only helps if someone copies the unexplained rows out.
| Claim about the new log | What Shopify documents | Owner you still assign |
|---|---|---|
| One log answers who changed everything | Changelog and Help say not every admin action is recorded, and history starts from when each change type began being recorded, shortly before 13 November 2026. | Name a fallback record for gaps: order Timeline, user management activity log, or POS activity log. |
| Every row names a person | Actors include staff, collaborators, apps, sales channels, Shopify staff, Via an app, and Actor unavailable. | For Via and Actor unavailable, name the app owner on the sheet. |
| Theme edits name the merchandiser | Help says theme actions can display Online Store as the actor when the work happened in the theme editor or Online Store channel. | Name who holds Online Store, then Themes permission, as the theme-publish owner. |
| You can keep the log outside Shopify | Entries cannot be exported. Keyword search is unavailable. Sidekick can open the page and cannot answer questions about entries. | Name who copies unexplained rows onto the weekly sheet, including timestamp, resource, actor, and action. |
| Everyone on the team can review it | The new table is limited by role. Other staff may still see the 250-row current list. | Name who has the new table, and who joins the review without needing their own filter access. |
If a change type still has no owner after the filter, freeze who may write it until someone accepts the row.
What merchants should do now
Run the first review on a quiet, closed week, so the filters are familiar before a live incident needs them.
- Confirm you have the new table, and if you still see the 250-row list, give the review to an owner or administrator who has the table, and keep taking screenshots until the rollout reaches you.
- Filter the last seven days for product, theme, and app-access changes, then open any row that does not match a planned merchandising change or release note.
- Sort the actors into named staff, Online Store, app or Via app, Shopify, and Actor unavailable, and write the owner next to each group.
- Copy the unexplained rows onto the owner sheet with the date, action, actor, resource, and the changed field when the details pane shows it.
- Repeat the review weekly, because eighteen months of retention only helps if someone is reading the new rows.
App governance stays a separate job. Use the rebuilt log as the native place to catch writers you already let in, and act when a resource you care about keeps landing on an actor nobody owns.
Conclusion
Back on that Tuesday morning, the hidden product now has a row in the log and a name beside it on the owner sheet. The 13 November 2026 rebuild gives you filters, row details, View activity links, and up to 18 months of entries, and it still leaves gaps, unnamed app actors, and no export, which is why the owner sheet is part of the job.
If product, theme, and app-access rows keep arriving without an owner, book a stack assessment and bring the filtered date range. A Shopify stack audit can list which staff roles and apps are allowed to write those resources, so the next unexplained hide arrives with a name attached.



