← All roles and access Roles and access

Shopify access for a developer

The role where access looks technical and is mostly about what happens when the project ends.

A developer needs themes and, where relevant, apps and API credentials. Orders, customers and finance are usually not required, and treating developer access as a synonym for full admin is a habit rather than a requirement. The part that matters most is credential hygiene at the end, because API keys and private app tokens outlive staff accounts.

What this person actually does

Developer work on a Shopify store is mostly theme code, sometimes a private or custom app, and occasionally a data migration. Each has a different access profile and only the last routinely touches customer data.

The reason developer access tends toward full admin is that debugging is unpredictable. Something breaks in an area nobody anticipated and broad access removes the friction of asking. That is a real cost, and it is still usually cheaper than the alternative of permanent unrestricted access.

The distinctive risk here is not the staff account. It is everything alongside it: API credentials, private app tokens, repository access, deployment keys. Removing the staff account and stopping there leaves most of the door open.

The two layers

Shopify permissions decide what they can do in the admin. The Store Huddle role decides what they see in the workspace. Both are needed, and they are set separately.

LayerFor this personWhy
Shopify staff accountRequiredStore Huddle runs inside Shopify admin
Shopify permissionsThemes, apps, sometimes APIScoped to the technical work
Store Huddle roleDeveloperTechnical rooms, not commercial ones
CredentialsTracked separatelyAPI keys outlive staff accounts

Shopify access to grant

Grant to the technical work, and keep a list of what else was issued. Shopify's permission labels change from time to time, so these are described by what they control rather than quoted as exact checkbox names. Check the current names in your own admin.

  • Themes, which covers most front-end work.
  • Apps, where they are building or configuring one.
  • API credentials, scoped to what the integration needs, and recorded so they can be revoked.
  • A development store or theme preview, which removes a good deal of the pressure for broader production access.
  • Reports, if performance work requires it, in preference to finance access.

Access to withhold, and why

  • Finance and payouts.
  • Customer records, unless a migration genuinely requires them, in which case it belongs in your data processing agreement.
  • Staff management.
  • Permanent production admin for work that could be done on a development store.

Rooms they belong in

Developers need the technical conversation and the deployment context, not the commercial rooms.

  • A development or technical room.
  • The room where deployments and releases are discussed.
  • Read access to the operational room during a launch, so they see the effect of what they shipped.
  • Not finance, management or supplier rooms.

Offboarding

Keep a written list of everything issued: staff account, API credentials, private app tokens, repository access, deployment keys. Removing the staff account alone is the commonest incomplete offboarding on this page.

Rotate any shared credential the developer had access to, rather than assuming it was only used by them.

If the work was done by an agency, the person may have rotated off the project long before the engagement ended. There is more in offboarding contractors.

Common questions

What Shopify access does a developer need?

Themes, and apps or API credentials where relevant. Orders, customers and finance are usually not required, and full admin is a habit rather than a requirement.

Should a developer have production admin access?

Prefer a development store or theme preview for the work, and grant production access narrowly and temporarily where debugging genuinely requires it.

What is most often missed when a developer leaves?

Everything that is not the staff account: API credentials, private app tokens, repository access and deployment keys. Removing the staff account alone leaves most of the door open.

Do developers need a Shopify staff account for the workspace?

Yes. Store Huddle runs inside Shopify admin, so every team member needs one. The Developer role then keeps them in technical rooms rather than commercial ones.

Related