Shopify staff accounts vs workspace invites: what the difference means

Two meanings of one phrase

"Give them access" is one of the most overloaded phrases in store operations. Depending on who says it, it means one of two quite different things, with quite different consequences.

A Shopify staff account is access to your store's admin. The person can sign in to Shopify and do whatever their permissions allow: view orders, edit products, issue refunds, change settings. This is access to the business itself.

A workspace invite is access to a tool your team uses. The person can participate in conversations and see what that tool shows them. It is access to coordination, not to the store.

Most access mistakes come from someone requesting the second and being given the first, because the first is what came to mind.

Why the conflation happens

Because for a long time it was true. If someone needed to know what was happening with orders, the only way to show them was to give them somewhere they could look at orders, and that meant admin.

So the reflex developed: new person, needs to be involved, create a staff account. The reflex is now often wrong, but reflexes outlive their reasons.

What a Shopify staff account actually grants

Shopify's permissions are reasonably granular, and you can restrict a staff account meaningfully. That is worth knowing, because it means the choice is not binary.

The things worth understanding:

• Permissions are per-area, not per-record. You can grant access to orders. You cannot generally grant access to some orders and not others.
• Staff account limits depend on your plan. On lower plans the number of staff accounts is capped, which means the decision has a cost as well as a risk.
• Some permissions imply others. Certain areas cannot be usefully restricted without breaking the workflow you granted them for.
• Customer data is the sensitive part. Order access generally means access to names, addresses and contact details, which brings data-protection obligations with it.

None of this makes staff accounts wrong. It makes them a decision that deserves a moment's thought rather than a reflex.

The test: does this person need to do things, or know things?

This is the whole decision, and it resolves most cases in seconds.

Doing things means changing the state of the store. Fulfilling orders, editing products, issuing refunds, updating inventory. That requires a staff account with the relevant permissions, and there is no way around it.

Knowing things means being informed and participating in coordination. Knowing a launch is Thursday. Being told stock is low. Being assigned a task. Discussing how to handle a complaint. None of that inherently requires admin access.

Run through your team. In most stores a meaningful number of people who have staff accounts only ever needed to know things, and were given the ability to do things because that was how the request was phrased.

Common cases

The social media freelancer

Needs to know what is launching, when, and what stock looks like. Rarely needs to change anything in admin. Frequently ends up with a staff account anyway, which grants access to customer data they have no use for and you now have to account for.

The virtual assistant handling customer emails

Genuinely needs to look up orders, so this one probably does need a staff account, scoped narrowly. The mistake here is usually granting more than orders because it was quicker than configuring properly. We covered the specifics in giving a VA access without giving away the store.

The seasonal packer

Needs to know what to pack and to flag problems. Whether they need admin depends entirely on whether your fulfilment happens in admin or on paper or in a warehouse system. Worth actually checking rather than assuming.

The agency that built your theme

Needed extensive access during the build. Almost certainly does not need it now. This is the most common source of lingering access, because nobody wants to send the awkward email and there is no natural moment that forces it.

The founder's partner who helps at weekends

The trickiest case, because trust is high and the arrangement is informal. High trust is a reason not to worry about intent. It is not a reason to skip the record of who has access, because the risk is a compromised account rather than a person behaving badly.

The practical arrangement

For most stores this works:

1. Staff accounts for people who change the store, scoped to the areas they actually need.
2. Workspace invites for everyone involved in coordination, which is usually a larger group.
3. Roles inside the workspace deciding what each person sees, so being in the workspace does not mean seeing everything in it.
4. A written record of who has what, reviewed when anyone leaves or a project ends.

This is how Store Huddle is built: team members are invited by email into the workspace and given a role that determines which rooms and categories they can see, without needing a Shopify staff account. Someone can be fully part of the conversation, receive tasks and see store alerts, without being able to sign in to your admin. Where they do need admin, that stays a separate and deliberate decision.

The audit worth doing today

List everyone with a Shopify staff account. For each, answer two questions: what do they change in admin, and when did they last do it?

Anyone who cannot answer the first question does not need the account. Anyone whose answer to the second is "months ago" probably does not either.

This takes about twenty minutes and is the highest-value security work most small stores can do, precisely because it needs no new tooling and no budget. It just requires someone to actually look.

Common questions