Lorixen.
EN

Giving a Developer Access to Your Shopify Store: Collaborators vs Staff Accounts

Short answer: For an outside developer or agency, use a collaborator account. They send a request from their own Shopify Partner account, you approve it with only the permissions the job needs, and you can remove it in one click when the work is done. A staff account suits someone who works inside your business day to day, such as an employee or a long-term contractor, and it uses up one of the staff seats your plan includes. Never hand over the owner login: it controls billing, payouts and the right to transfer the store, and you cannot limit what someone does with it.

Collaborator or staff: which one fits

Question Collaborator account Staff account
Who is it for Agencies, freelancers, app developers with a Shopify Partner account Employees and people working in your business
Who starts it The developer requests access You invite them by email
Counts toward staff limit No Yes
Permissions Chosen by you per request Chosen by you per user
Typical duration A project Ongoing
Best removal route Remove collaborator Remove or deactivate staff

If your developer works through an agency, the request will usually come from the agency's partner organisation, which lets the agency manage which of its people can reach your store. Shopify explains the mechanics in its collaborator accounts help page.

Step 1: Set the collaborator request code

Shopify lets you require a code before anyone can send you a collaborator request. This stops strangers from asking for access in the hope that someone approves by accident.

  1. In the admin, open Settings > Users (shown as Users and permissions in some versions).
  2. Find the Collaborators section and choose whether anyone can send a request or only those with a request code.
  3. Choose the option to require a code and note the code shown.
  4. Give the code to your developer through a channel you trust, such as a phone call or your project tool, not a public message.

Change the code after the project if you shared it widely.

Step 2: Approve the request with narrow permissions

When the developer submits their request, the store owner (and staff with the right permission) receives a notification and email.

  1. Open the request and check the name and partner organisation match the person you hired.
  2. Review the permissions requested. Developers often ask for broad access because it saves them time later.
  3. Untick what the job does not need. A theme redesign usually needs Online Store (themes, pages, navigation) and perhaps Products. An app integration may need Apps and the specific data the app reads.
  4. Accept the request.

You can edit collaborator permissions later, so start narrow and add when a real need appears.

What to keep restricted

Some areas carry financial or legal consequences. Keep them closed unless there is a specific reason and you are present when they are used.

  • Payments and payouts settings: bank details and payout schedules.
  • Billing: plan changes, app charges and payment methods.
  • Store ownership and transfer: only the owner should ever touch this.
  • Customer data exports: necessary for some migrations, but it moves personal data out of Shopify, so agree in writing how it will be handled.
  • Staff management: a collaborator should not be able to add other users.
  • Domains: connecting or removing domains can take the site offline.

The full list of areas is set out on Shopify's staff permissions page; collaborator permissions use the same categories.

Why the owner login must never be shared

Sharing the owner's email and password feels quicker, but it causes problems that are hard to undo.

  • Shopify cannot tell your actions from theirs in the activity history.
  • Two-step verification codes go to your phone, so you end up forwarding codes, which defeats the purpose.
  • The person could change the password or the owner email, effectively taking the store.
  • Shopify's terms expect each person to use their own account.

If a developer insists on the owner login, treat it as a warning sign.

When a staff account is the better choice

Pick a staff account for:

  • an in-house marketer or customer service assistant
  • a contractor who will handle orders or content for months
  • someone without a Partner account

Invite them under Settings > Users > Add staff, select permissions the same way, and make sure they turn on two-step verification. Staff seats depend on your plan, so check your plan details before inviting.

Offboarding checklist when the work ends

Access should end on the day the project ends, not months later when you remember.

  1. Open Settings > Users, find the collaborator and choose Remove (or reduce permissions if a support period continues).
  2. Review installed apps. Remove test apps or apps the developer installed that you no longer use, and check their charges in billing.
  3. Check theme files: delete unused duplicate themes and keep one backup copy of the previous live theme.
  4. Rotate any API credentials or custom app tokens created for the project, and remove custom apps that are no longer needed.
  5. Change the collaborator request code.
  6. Ask the developer for a short handover note: what was changed, which apps were added and where any code lives.
  7. Remove access in other tools you shared, such as your domain registrar, email service or analytics.

FAQ

Can a collaborator see our customers' personal data?

Only if you grant permissions that include customers or orders. Grant those only when the work requires them.

Does a collaborator account cost anything?

Collaborator accounts do not use a staff seat. Check your plan for any current limits on the number of collaborators.

Can we approve access without the code?

If you require a code, requests without it cannot be submitted. Turn the requirement off temporarily only if a trusted partner has trouble.

What if a former developer still has access?

Remove the collaborator account now and review the activity log for changes made after the project ended.

If you are about to bring in a developer and want the access set up properly from day one, talk to us and we will help you plan permissions and the handover.

Sources

WhatsAppBook a call