Reviewed October 21, 2026
Shopify staff permissions: roles to set up before you invite anyone
Handing the owner login to helpers is the most common small store security mistake. How Shopify permissions and roles work, who needs what, and the habits that keep access tidy.
Why individual accounts matter
Every person in your store needs their own login. Shared credentials mean no audit trail, no clean way to remove access when someone leaves, and no two factor protection worth the name. When something changes unexpectedly in a store where five people share one password, you cannot even answer the first investigative question, who did it.
Shopify staff accounts and roles exist to solve exactly this. A role bundles the permissions a job needs, orders access for fulfillment help, product access for a catalog contractor, marketing access for an agency, and nothing beyond. Setting roles up before inviting people is ten minutes of work that prevents the most common access messes stores create for themselves.
Mapping roles to real jobs
Start from tasks, not seniority. The person packing orders needs orders and fulfillment, not settings or billing. A freelance designer needs theme access, ideally on a duplicate theme, and does not need customer data. An accountant needs reports and finance views, not the ability to edit products or refund at will.
Agencies and developers are the sensitive case. Grant what the engagement requires, for the duration it requires it, and prefer collaborator style access where available so their access lives under their own organization accountability. A standing full access account for an agency you stopped using last year is a liability with no upside.
The permissions to guard most carefully
Settings, billing, and user management are the keys to the building. Very few people need them, and changes there can lock owners out or redirect money. Keep that tier to the owner and at most one trusted deputy, and review it whenever the team changes.
Financial permissions deserve the same care. Refunds, gift cards, and payout details are where internal fraud and social engineering both aim. Two factor authentication on every staff account, no exceptions for convenience, is the single control that defeats most account takeover attempts against small stores.
Keeping access tidy over time
Review the staff list quarterly. Remove finished contractors, departed employees, and duplicate accounts, and downgrade roles that quietly grew broader than the job. Access expands by accident and almost never contracts on its own, so the review has to be a calendar habit rather than a reaction to an incident.
Document who has what and why in one page your future self will thank you for. When a question arises mid incident, that page turns an hour of archaeology into a minute of reading. Small stores think they are too small for this discipline right up until the first access scare proves otherwise.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Test orders on Shopify: Bogus Gateway, test mode, and what to check, Setting up fulfillment locations and order routing in Shopify, and Backing up a Shopify store: what to save and how often.
Frequently asked questions
How many staff accounts can a Shopify store have?
Limits depend on your plan, and newer Shopify setups use role based access with organizations in mind. Check your current plan limits in settings, and remember that permissions design matters more than the count. Ten tidy role based accounts beat three shared logins at any plan level.
Should I give my developer full access?
Give the access the work requires, for as long as it requires it, and prefer collaborator access where offered. Full permanent access for a finished project is unnecessary risk. A good developer expects scoped access and will tell you what they actually need.
What is the most important staff security setting?
Two factor authentication on every account, enforced without exceptions. Most store takeovers start with a phished or reused password, and a second factor blocks the large majority of those attempts regardless of how the password leaked.
How often should I review staff permissions?
Quarterly as a habit, and immediately whenever someone leaves or an engagement ends. Access reviews decay fast in small teams because roles change informally. A short scheduled review keeps the list matching reality instead of history.