Shopify staff account vs collaborator access when hiring help.

Staff account = a person who belongs on your team for ongoing work. They get a seat under Users and permissions, you choose categories, they stay until you remove them.

Collaborator access = Shopify’s partner / contractor path for a scoped job. You approve a request, pick scopes, they work, you revoke. Built for a clear end date.

This page is the fork. The step-by-step invite, scopes, clock, and revoke walk for a 72-hour install lives on the collaborator access how-to. Do not treat that page as “always create staff” or this page as “always invite collaborator.” Match the seat to the job.

Use staff when the person will keep working in your store week after week: customer support, order ops, a marketing hire who lives in admin, a VA who answers Inbox every morning.

• They need recurring access without re-approving a partner request each time.
• You want their login tied to your store’s staff list, not a Partner Dashboard collaboration request.
• The role is ongoing — not a three-day wiring job with a handoff note.

Staff is still not “give them everything.” A CS hire rarely needs bank or domain transfer. Least privilege applies to staff seats the same way it applies to collaborators.

Prefer collaborator access when the job is short, scoped, and ends: a freelancer wiring notifications, an agency doing a one-week audit, or a 72-hour AI ops install on one live store.

• Clear start and end. You want revoke to be the normal last step, not an awkward firing of a staff seat.
• The operator already works through Shopify Partners. You approve their request; you do not invent a fake permanent employee.
• You are buying a fixed deliverable — not adding a teammate to payroll-shaped access forever.

Latch AI Ops runs on collaborator access for that reason: one live store, United States offer, clock starts when access is in, revoke after handoff. Details on the collaborator access playbook.

Sharing the store owner password is not a third option. It is how stores lose audit trails, leave silent full access open, and cannot revoke one person without changing the login everyone uses.

If a vendor asks you to email the owner password “just for speed,” that is a red flag whether they prefer staff or collaborator language. Latch AI Ops does not take owner passwords. Store URL is collected at checkout; access plus a delivery thread is how the work runs.

Creating a staff seat named “Owner backup” for a vendor is the same mistake wearing a different label. Name the person, name the scopes, name the end date.

Checkbox labels move by Shopify plan and year. The principle does not: turn on only what the job needs this week.

• Short ops / notification / lead-capture install: usually Apps and channels; Settings that touch notifications or checkout wiring; Online store / Themes only if a theme snippet is in scope; Orders / customers read to verify on real data.
• Ongoing CS staff: Inbox / orders / customers as needed — still not bank, payouts, or domain transfer by default.
• Not needed by default for either path: Shopify Payments full ownership, bank accounts, Domains transfer, Staff that can create other owners.

If the only pain is flooded Inbox threads, start on the Inbox flooded playbook before you widen anyone’s access. Access is the door. The bug may be process, not permissions.

Collaborator: when the delivery thread says done, remove them the same day if you can. Leaving unused collaborator access open is how stores accumulate silent admin accounts.

Staff: when the role shrinks, reduce scopes. When they leave, remove the seat. Do not keep “temp help” staff with full Apps + Settings for six months because nobody owns the list.

Keep a short internal note: what changed, which apps, where alerts land. That note is for you — not a marketing case study. Latch has not published customer proof because there are no customers yet.

Stay DIY if you only needed the fork: staff for people who stay, collaborator for a scoped short job, never the owner password, revoke when done. This page is enough for that decision. No agency required to click Create staff or Approve collaborator.

Pay for help when the work is connecting the stack you already have — lead capture on the live store, ops alerts in a channel you check, checkout-ready wiring — inside a fixed 72-hour window after collaborator access is in. That is the Latch AI Ops install.

What $997 USD one-time buys: that install on one live Shopify store. Clock starts on collaborator access. Operator is Nico. Checkout is on Whop. You can revoke access after handoff. We do not take owner passwords.

Other shops’ public ranges, not testimonials: a small focused app / notification wiring job often sits in the same $500–$2,500 band. A full CX agency retainer or a permanent staff hire is a different product. $997 is the cheap end of wiring three systems on one store — not a revenue or ticket-cut guarantee.

What it does not buy: guaranteed fewer tickets, recovered checkout revenue, or a published case study. You are buying the install and the access model — collaborator, not owner password, not a forever staff seat by default.