Shopify team collaboration, permissions, and a 30/60/90-day operating roadmap
5 parts · 2 checkpoints · 1 free / 4 member parts →
This roadmap connects staff roles, store permissions, collaborator accounts, sensitive permissions, release governance, RACI, and exception recovery in one readable evidence card; it does not read a current store or treat a job title as permission proof.
This lesson answers
Make the next repair repeatable
The previous lesson selected actions from weekly signals. This operating review assigns who acts, who checks, and how to recover if something goes wrong. If you arrived here directly, use the two store examples below before choosing your team state. The 30/60/90 stages are review points, not dates that guarantee expansion.
TrekCup: more orders and more delivery questions
In the UK market, TC-20OZ-OLIVE moves from £42 to £39. Paid orders rise from 46 to 58 and delivery questions from 3 to 11. These before-and-after records do not show that the price cut caused the questions. Start with three inquiries and three orders from the same scope, then compare the product page, checkout, confirmation email, and fulfillment record.
PetNest: separate page investigation from order exceptions
The other example store, PetNest, is investigating the SlowFeast product page and two orders. PN-1043 has an empty tracking field; PN-1044 has near-duplicate writes. Flow is the automation workflow, and a Flow run is one execution record. Page behavior, order facts, and automation logs answer different questions, so assign the relevant technical, operations, and data checks separately.
The 58, 54, and 57 below are raw page observations, not order counts. The example does not supply a complete metric name and unit, so they cannot establish whether performance improved. Together with orders moving from 39 to 40, they illustrate why each record needs its own source, tool, time window, and reviewer.
Working terms used below
Readback / check the actual result
Reopen the page or record after a change to check what customers see and what the system shows.
Recovery object / what to restore
The saved theme copy, previous price, original workflow, or prepared manual process.
Shared assets / material the next person can find
Dated order, page, change, and exception records with their scope and review results.
RACI
Separate the person doing the work (R), accountable for it (A), consulted beforehand (C), and informed afterward (I). One person may cover several roles; the table itself does not grant admin access.
An “allowed” or “reader” surface means a specific page, field, log, or theme copy. Ask which object the task will inspect or change.
Choose team state and risk first because a roadmap must start from a verifiable current problem, not a job title or meeting schedule. Team state describes whether the capability is repeatable; risk identifies which customer path, shared asset, or access boundary may fail first. Their intersection tells you whether the first governance asset should be a replay record, recovery object, access review, or capability exercise.
Do not treat “someone is responsible” as “the fact has been read back.” A PetNest access or incident risk must resolve to visible surfaces, an actual task, blocked states, and recovery readback. A TrekCup market route must resolve to entry, address, promise, and version. The choices below help ask the right questions; they do not sign off current store permission or production results.
Turn 30/60/90 into an evidence plan that can be checked by day
Which role is missing first?
Self-check not answered
30/60/90 is not an automatic maturity schedule or a promise that a team will become mature on a date. It is a set of review windows. Each window must state what was completed, what evidence lets another owner reproduce it, what pauses the work, and which recovery object is used when the work is incomplete. A date without evidence is a calendar, not a route.
Series start
Member practice follows
The role split, approval path, handoff card, and roadmap record live in the member workspace.
Pro · Parts 2-5 · 4 parts
Members: full exercises and records
This part includes
- Must keep
- Name all four roles for one automation
- The handoff card names the recovery confirmer
Pro $20 / monthYearly $16 / month
Choose a plan, sign in with your email or Google account, and complete payment. You'll have instant access to all member benefits.
- Unlock every premium lesson
- Advanced tools and member resources
- Member-requested courses and ongoing updates
- Pro community and priority support
Checking your membership…
What's the difference between monthly and yearly?
Yearly plans save you 20% with annual payment. Monthly plans offer more flexibility for short-term needs.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Does a one-person Shopify operation need an operating roadmap?
Yes, without turning it into an HR system. One person can cover business, content, technical work, and review, but each high-risk move still records why it changes, what actually changed, which customer path reads it back, and what gets restored on an exception. That prevents next week from depending on memory.
- When must responsibilities be separated?
Separate business decision, actual operation, and later readback in the record when a move affects customer-visible price, delivery, payment, fulfillment, sensitive scope, or a theme, field, or automation change that cannot be recovered quickly. Two people can complete those moments at different times; this does not require a heavy approval system.
Sources
Sources: 8Last checked
Shopify Help Center: Store permissions (opens in a new tab)Checked
Shopify Help Center: Sensitive permissions (opens in a new tab)Checked
Shopify Help Center: Collaborator accounts (opens in a new tab)Checked
Shopify Help Center: Activity logs (opens in a new tab)Checked
Shopify Help Center: Manage users (opens in a new tab)Checked
Shopify Help Center: Working on client stores (opens in a new tab)Checked