An online product page can be changed by more systems than the store editor suggests. Catalog roles may alter the title, description, price, inventory, media, or publication status. Theme and code roles can change how every product is displayed. Apps, feeds, files, analytics, and advertising accounts add indirect paths. A useful audit traces all of them and ties each permission to a current job.
Define the page and its connected systems
Choose one real product page and record its store URL, product identifier, sales channels, theme template, media files, feed destinations, and connected apps. This keeps the audit concrete. Then list the systems that can affect those elements: the commerce admin, product information tool, inventory system, theme repository, file library, Merchant Center, advertising account, analytics, review app, subscription app, and automation platform.
For each system, record the account owner, administrators, assigned role, actual capabilities, last confirmation date, and the reason access remains necessary. Include external agencies, app partners, temporary staff, groups, API credentials, and service accounts.
Separate catalog work from structural work
Shopify's current store-permissions documentation separates product actions such as viewing, creating or editing, editing price, exporting, and deleting. It also treats Themes and Edit code as distinct permissions, and notes that some permissions depend on others. Consult the official Shopify store permissions guide while translating a role into actions.
Build a matrix for the page. Columns can include view products, edit copy, edit price, edit inventory, upload files, publish to channels, delete products, change the theme, edit code, install apps, export data, and manage users. Mark required, not required, or unknown for each person or system. Unknown is a follow-up item; it is not permission to leave a broad role unexplained.
Check whether a content writer can work without price, deletion, theme, or code rights. Check whether an inventory operator needs product copy access. Keep emergency administrator access separate from ordinary daily work and ensure the business, rather than a departed contractor, controls the primary owner account and recovery path.
Inspect feed and marketplace access
A product page may also be represented in Google Merchant Center. Google's people and access guide explains that access types and roles apply in the Merchant Center interface and Merchant API, and that account administrators manage people, apps, and stores. Review administrators first, then standard users, email-only contacts, connected apps, and store associations.
Compare the store's product identifier, landing page, price, and availability with the feed destination. The audit is about control paths, so record which account or integration sends each field and who can change that connection. Do not assume that removing a store user removes a separate Merchant Center user or API client. Verify both systems.
Check apps, files, and automation
List apps that can read or write products, inventory, orders, files, themes, or customer data. Record the visible scope, business purpose, billing owner, and removal test. For media, check the store file library, cloud drive, design tool, and CDN. A stale file-library role may permit replacing an image even when the person cannot edit the product record directly.
Review automations for bulk edits, inventory synchronization, translation, feeds, and scheduled publishing. Test with a noncritical draft or staging product before revoking a live integration. Preserve a rollback record for theme or code changes.
Verify the result from end to end
Apply changes in a controlled order: confirm business-owned administration and recovery, remove departed users, reduce unnecessary product actions, clean up external feed access, then revoke unused apps or credentials. Avoid changing several integrations at once because that makes a missing price, image, or availability signal harder to diagnose.
Finish by opening the product in the admin, its public page, each active sales channel, and Merchant Center. Confirm the expected title, price, availability, media, and destination URL. Have an intended editor perform a harmless draft change and confirm that a viewer cannot perform an edit. Record evidence, unresolved access, and the next review date. The completed audit should explain both who can edit the product record and every other route that can change what shoppers see.
Sources
- Store permissions — Shopify Help Center
- Manage people and access levels in Merchant Center — Google