The limit that arrives without warning
Most store owners meet their staff account limit at the worst possible moment: a new hire starts, somebody goes to set them up, and Shopify says no. It is not a well-advertised constraint, it does not appear in the onboarding flow, and it tends to surface on somebody's first morning.
The cap is per plan. Lower plans include a small number of staff accounts, higher plans include more, and the number is a hard limit rather than a soft one with an overage charge. There is no way to buy one extra seat. You move up a plan or you do not add the person.
That pricing shape is what makes this worth thinking about in advance rather than on the morning it bites. The gap between plans is usually large relative to the value of one more login, so the decision is rarely about that person. It is about whether your whole operation has outgrown the tier.
What a staff account actually gets you
A Shopify staff account is a login to your store's admin with a permission set attached. Whoever holds one can be scoped tightly, down to specific sections, but they are consuming a seat whether they use ten permissions or one.
This is the part people get wrong. A warehouse assistant who only needs to mark orders as fulfilled costs the same seat as a general manager with full access. The cap does not care how much of admin somebody uses, only that they can open it.
The practical consequence is that low-touch people are the expensive ones. Somebody who logs in twice a week to do one job is using the same scarce resource as the person who lives in admin all day, and they are usually the first to get squeezed out when the cap bites.
The four ways teams get around it, ranked by how bad they are
Every store that hits the cap does one of four things. They are not equally sensible, and the two most common are the two worst.
1. Sharing a login
The most common workaround and the one to avoid. Two or more people use the same staff account, usually with the credentials in a message somewhere.
The immediate problem is that the audit trail becomes fiction. Shopify records who did what by account, so when a discount is applied wrongly or an order is cancelled, the log says a name that could be any of three people. You lose the ability to answer a basic question honestly.
The slower problem is offboarding. When one of those people leaves, the correct move is to change the password, which locks out everybody else on that login until they are all told the new one. In practice nobody does this, so the leaver keeps access indefinitely. A shared login has no leaving date.
2. Reusing a departed employee's account
Slightly better than sharing, still bad. The account of somebody who left gets renamed and handed to the new person.
This keeps one person per login, which is the important property, but it corrupts history in a subtler way: every action the previous holder took now appears to have been taken by the current one. If you ever need to establish who processed a refund in March, the answer is wrong and looks right.
If you are going to do this, at least change the name and email immediately rather than leaving it for later, and write down the handover date somewhere you will find it.
3. Upgrading the plan
The honest answer, and often the right one. If the constraint is genuinely that you have more people who need admin than your plan allows, the plan is the wrong size.
The test is whether the extra people need admin itself or need something admin happens to contain. That distinction is the whole of option four, and it is worth checking before paying a year of the difference.
4. Not giving them admin at all
The option most teams do not consider, because the request arrives as "can you set up an account for Sam" rather than "Sam needs to see order statuses".
A surprising share of the people you want to add do not need Shopify admin. They need to know which orders are outstanding, or to be told when something is out of stock, or to be able to say they have done a thing. Those are information and coordination needs, not administration needs, and admin is an expensive way to meet them.
Working out which of your people actually need admin
Go through everybody who has an account, or wants one, and answer one question for each: what do they change in Shopify? Not what do they look at, what do they change.
People who change things, meaning they edit products, process refunds, adjust inventory, fulfil orders or alter settings, need admin. That is what admin is.
People who only need to know things, or to communicate about things, do not. A fulfilment assistant who is told what to pick and confirms when it is packed is in this group. So is a marketing contractor who needs to know when a product is back in stock. So, usually, is anyone described as being "kept in the loop".
In most small stores this exercise reclaims two or three seats, which is frequently enough to defer a plan upgrade by a year.
The one case where you should just upgrade
If the people you are trying to add genuinely change things in Shopify, stop optimising and move up. Working around a real need for admin access produces shared logins, and shared logins produce a store where nobody can say who did what.
A useful way to frame the cost: the gap between plans, divided by twelve, against the cost of one incident where you cannot establish who cancelled an order. Most owners find the second number is larger than they assumed, because the cost is not the order. It is the hour spent working out what happened and the conversation with the person you wrongly suspected.
What to do this week
- List every staff account and put a name against it. Anything you cannot attribute to exactly one person is a shared login, and it is your most urgent problem.
- For each account, write what that person changes in Shopify. Blank answers are candidates for removal.
- Check for accounts belonging to people who have left. These are the cheapest seats to reclaim and the most dangerous to leave.
- Decide, before the next hire rather than during it, what your rule is: who gets admin, who gets a coordination tool, and who gets told things.
The contractor problem, which is the same problem wearing a hat
Agencies, freelance developers and virtual assistants are where the cap gets quietly wasted, because their access tends to be granted once and never reviewed. A developer who did a theme project in February still holds a seat in November, and nobody has thought about it since the invoice was paid.
Two habits fix most of this. First, every external account gets an end date at the moment it is created, written somewhere you will actually look, such as the calendar rather than your memory. Second, when the work finishes, removal is part of finishing rather than a separate task that gets deprioritised behind paying work.
The awkward version is the agency on a retainer, where the engagement has no end date by design. There the review has to be calendar-driven instead: once a quarter, look at every external account and confirm the person still works on your store. Agencies change staff, and the individual who left the agency in June may still have a login to your admin.
What the cap does not restrict
Worth stating, because the confusion causes people to upgrade earlier than they need to.
- Customers. Accounts your shoppers create are not staff accounts and do not consume the allowance, however many you have.
- Apps. An installed app is not a staff member. The permissions an app holds are separate from your staff count.
- People who only receive information. If someone is told what to do and confirms it is done, without ever changing anything in Shopify, they do not need a login at all. This is where most reclaimed seats come from.
Related reading: staff accounts and workspace roles covers the conceptual line between the two, and offboarding contractor access covers removing access cleanly when somebody leaves.
Common questions
How many staff accounts does Shopify include?
It varies by plan, with lower plans including a small number and higher plans including more. Check your current plan in admin rather than relying on a figure from an article, because plan contents change and a stale number is worse than none.
Can I buy extra staff accounts without upgrading?
Not as a standalone add-on. The count is tied to the plan, which is why hitting the cap forces a larger decision than adding one person would suggest.
Is sharing a staff login against the rules?
Set aside the rules: it breaks your own audit trail and makes offboarding impossible to do properly. When a shared login's holder leaves, the only clean response is changing the password and re-telling everyone else, which almost nobody does.
Do all my team members need Shopify staff accounts?
Only the ones who change something in Shopify. People who need to know what is happening, or to coordinate about it, can often be served without admin access at all, which is usually where reclaimed seats come from.
What happens to a staff account when someone leaves?
Nothing automatic. You remove it, which frees the seat. Accounts belonging to people who left months ago are common and are both the easiest seats to reclaim and the most serious open access risk.