Shopify access should tell you who is acting and why that person needs each permission. Confirm owner control first, give each person an individual login, and assign roles for their work. Then verify two-step authentication, recovery arrangements, and offboarding. Sharing the owner password does not resolve an invitation or permission problem.
10 parts · 3 checkpoints
Show all 10 parts
- 01Separate identity, roles, and ownership
- 02Build the permission matrix from actual work
- 03Confirm the store and its owner
- 04Create roles, then inspect each permission
- 05Handle staff invitations and collaborator requests separately
- 06Verify sign-in and prepare recovery after a lost phone
- 07Offboard every access path
- 08Practise the theme-development decision, has a checkpoint
- 09Keep the access and revocation record, has a checkpoint
- 10Work it out: which account carries the widest exposure
Key point Give every access grant a purpose and an owner
Your permission matrix should name the person, job, role, store scope, approver, and review date. A role page shows configured access. Identity, working authentication, recovery-code custody, and successful revocation require separate checks.
The example is a shop preparing to sell desk-organization products to the US, with USD prices and English service. A long-term owner controls the store, an operator handles products and orders, and an external developer changes the theme. These are teaching plans, not confirmed settings or evidence of a US entity, payment eligibility, or launch readiness. Begin by listing the people and access needed in your store; check the status of General settings separately.
Questions this lesson answers
- How do an owner, staff user, and organization administrator differ?
- What access do operations, support, finance, and developers need?
- How do I confirm the owner and the correct store?
- Why shouldn't I use Full permissions to make a missing feature appear?
- How do staff invitations and collaborator requests differ?
- How do I verify 2FA and recover after losing a phone?
- How do I revoke user, app, and API access when work ends?
- What should the access, authentication, and revocation record contain?
Separate identity, roles, and ownership
A user account is a person's sign-in identity. A permission allows a particular action, such as viewing orders, editing products, or exporting customers. A role groups the permissions needed for a job. After assigning a role, check which stores the person can enter. Matching role names do not establish matching store access or effective permissions.
The Store owner holds the store's ownership role, and each store has one owner. An organization can contain several stores, with separate organization-owner and administrator responsibilities. An administrator role does not make someone the Store owner, and granting every permission does not transfer ownership. Check the selected store, role category, and scope before deciding who can invite users, manage roles, or perform owner-only work.
Staff users are people you invite to do ongoing work. A collaborator account lets an external Shopify Partner request access for you to review. It does not use a regular staff seat or confer ownership or unlimited access. Calling an agency a collaborator does not verify the person making the request or explain the permissions they need.
Authentication is another distinction. Two-step authentication, or 2FA, checks an additional credential beyond a password, such as an authenticator code or security key. Shopify also uses the label Secure sign-in method, which can involve a passkey or two-step authentication. A requirement switch does not prove that a user has configured and tested 2FA.
Regular staff access depends on the plan. Basic and Starter currently do not allow additional Shopify admin staff; Grow and higher plans have the allowance for each plan: zero on Basic and Starter, five on Grow, fifteen on Advanced, unlimited on Plus. Development stores follow different seat rules. If you work alone without staff seats, use your own owner account securely instead of sharing it to simulate a team. Assess the appropriate plan when another staff member needs access, and use collaborator access only for work that fits that account type.
Build the permission matrix from actual work
The example developer needs to adjust theme sections on a product page. That task does not require a customer download or payment-settings change. Writing down the task makes the requested access easier to assess. Least privilege means granting only the scope needed for an approved job. A new task can justify a new permission, with an approver, expiry, and removal plan.
Before opening the admin, list everyone who touches the store, including part-time staff, agencies, developers, and report-only users. Review product, order, customer, marketing, analytics, finance, theme, settings, and app tasks. Prepare a controlled password vault, recovery-code custody process, and offboarding checklist. The names below describe jobs; they are not promises that Shopify provides an identically named preset.
Starting access boundaries for the desk-organization shop
Store owner
- Access to consider for the job
- The long-term responsible person controls ownership and recovery arrangements.
- Default boundary and review
- Do not share the owner password. Where staff accounts are available, separate routine work by job.
Operations
- Access to consider for the job
- Maintain products, handle assigned order work, and manage approved discounts.
- Default boundary and review
- Exclude payment and user management by default. Approve actions such as refunds separately when the job requires them.
Support
- Access to consider for the job
- Read the orders and customer communication information needed to provide service.
- Default boundary and review
- Order lookup does not justify payment settings, app installation, or full customer exports.
Finance read-only
- Access to consider for the job
- Begin with the reports, orders, or financial views needed for the responsibility.
- Default boundary and review
- Inspect the exact financial permissions and organization scope. Exclude theme editing and unrelated payment changes.
Developer
- Access to consider for the job
- Themes and approved related apps, with a project revocation date.
- Default boundary and review
- Keep customer export, billing, and payments off by default. A debugging exception needs a task, data scope, and time limit.
External collaborator
- Access to consider for the job
- Verify the requester, project, and approved permissions.
- Default boundary and review
- Remove access when the project ends. Name the store-side approver and person responsible for removal.
For example, support may need an order to answer a shipping question. That does not require changing the payment account. Keep those actions separate in the matrix. Add a person or redacted identifier, role, store scope, reason, approver, review date, and evidence location to each row. A plan is not a verified assignment: mark the row passed only after the saved access and safe job tests agree.
Confirm the store and its owner
Before inviting anyone, establish which store you are managing and who controls it for the long term. Being able to open the admin establishes access, not Store owner status. In the example, handing over theme work must still leave ownership and recovery under the long-term owner's control.
Confirm ownership and the people who need access
Check the selected store and Store owner
Where in the UI: SettingsUsers
Check the store name, admin address, and Users list. Open the user details to confirm the Store owner. For an organization, distinguish Organization owner, Organization administrator, and Store owner, including the stores each person can access.
You should see
Separate the owner account's purpose, long-term responsibility, routine work accounts, and recovery responsibility.How to confirm
The responsible person confirms individual account control. The role belongs to the correct store, and nobody else uses the owner password.If it goes wrong
If ownership or organization scope is unclear, pause invitations and access expansion. Ask the long-term owner to resolve it before changing a similarly named store.Keep as evidence
Record a redacted account identifier, responsible person, review time, and evidence location. Do not record passwords or actual recovery information.
Use the list to distinguish people, status, and roles. The image shows a historical English development-store view; the historical Chinese reference is 设置 → 用户. When labels change, also check the page title and complete target area.
Admin path: Settings > Users

Historical development-store example. Active and role labels help inspect responsibility; they do not establish current invitee identity, staff-seat availability, 2FA, or recovery status.
The active rows carry different owner and administrator roles. Inspect each person rather than treating Active as equal authority. In the user's details, review assigned roles and the stores they cover. The next image shows owner roles and location scope; it does not show a removal control.
Admin path: Settings > Users > user details

Historical owner-access details, not a collaborator-removal screen. Use it to inspect roles and scope. It does not establish completed revocation, and ownership should not be changed to reproduce the image.
For your own evidence, keep the page title or breadcrumb, complete relevant area, and actual result. Redact names, emails, store addresses, and other sensitive values. A capture shows one moment; review again after a setting change, role change, or departure.
Create roles, then inspect each permission
Name roles for their purpose, such as Operations, Support read-only, or Developer. Admin 1 says nothing about the approved work. Start by reviewing existing roles. Roles managed by Shopify cannot be freely customized, and the role categories you can create or manage depend on the plan, organization, and your eligibility.
In a single non-Plus store, the owner or an eligible Administrator can manage users. Within an organization, a Store owner can manage users for their store but cannot create or manage roles on that basis. A Store user administrator cannot create or edit roles either. An eligible organization administrator should check organization and plan conditions before creating organization roles. Seeing Add role does not establish that every user can grant the same access in every store.
Save the role and test the work it permits
Create a role with a defined job
Where in the UI: SettingsUsersRoles
Review existing roles. If a custom role is needed and you are eligible, choose Add role, select its category, and enter a name and job description. Select the required Permissions and, where available, approved app access, then Save.
You should see
Keep a role with an identifiable job, responsible person, permission scope, and review date.How to confirm
Reopen the role and compare the saved permissions with the matrix. A role list shows names, categories, and user counts; it does not inspect the individual permissions for you.If it goes wrong
If the entry is missing, check the store, your eligibility, plan, and role category. If a Shopify-managed role cannot be edited, assess a suitable predefined or custom role without widening everyone's access.Keep as evidence
Keep the role name, job description, permission matrix, approver, and next review date.Reduce permissions and test allowed and denied actions
Inspect relevant groups such as Products, Orders, Customers, Settings, themes, and apps. Support does not receive payment or app-install access by default; developers do not receive customer exports; finance read-only does not receive theme editing. Check every assigned role because their permissions accumulate.
How to confirm
An authorized test user should check permitted views and changes using safe test objects, and confirm that excluded actions are denied. Do not use real refunds, payments, or customer exports as permission tests.If it goes wrong
When a job is blocked, identify the missing permission, store or organization scope, plan, or resource condition. Add only justified access and retest. Remove excess access before retesting; do not hide the issue behind Full permissions.Keep as evidence
Record allowed and denied results, the permission rationale, exception approver, expiry, and retest time.
The historical Chinese reference is 设置 → 用户 → 角色. This image shows the role list, not an expanded permission editor. Open an individual role to inspect its details.
Admin path: Settings > Users > Roles

Name, Category, and Users help locate a role. Products and Orders permissions are not expanded here, and this development view does not establish current staff or role availability on your plan.
Reopen the relevant area after saving and check required fields, validation messages, and the saved result. A visible button shows that an entry is available on that page. Continue when the specific job test passes and unrelated high-risk access remains off. Review the matrix when a person changes jobs, an app asks for more access, or an exception expires.
Handle staff invitations and collaborator requests separately
Staff members accept invitations through their own email. External Shopify Partners request collaborator access for a project. Do not put contractors behind one shared administrator login or send the owner password through chat. The example developer's theme task does not justify customer export; ask for the actual debugging task before considering such a request.
Assign access to the right person
Invite an individual staff user
Where in the UI: SettingsUsersAdd users
Check the plan's user allowance and your management eligibility. Select Admin user, enter the person's individual email, and assign roles under Roles or Roles and groups. Review Permission summary and store scope, then save the invitation. Keep the secure-sign-in requirement unless there is a justified reason to change it.
How to confirm
Confirm the email identity, invitation status, and assigned roles. After accepting, the person signs in to the correct store and tests the job. Pending does not mean access is already working.If it goes wrong
An eligible administrator should handle an expired invitation through the current invitation process. For a missing feature, return to the role, store, and plan checks instead of sharing the owner login.Keep as evidence
Record a redacted email identifier, role, invitation date, acceptance status, approver, and retest result.Review the collaborator request and set a project end date
Where in the UI: SettingsUsersRequests
An eligible person gives the collaborator request code from Security to the verified Partner. After the Partner requests access, inspect the expected person, project, and permissions under Requests. Review the generated role or assign suitable existing roles before accepting; what you may edit depends on organization eligibility.
How to confirm
Grant only the project scope. Record the store-side owner, end date, and removal action. A request code enables a request, not a login; keep it out of public captures and notes.If it goes wrong
Leave unexpected requests unaccepted and contact the known Partner directly. If they ask for the owner password, use collaborator access or an eligible restricted account instead.Keep as evidence
Keep a redacted requester identifier, approved scope, approver, project end date, and revocation owner.
Collaborators do not use regular staff seats, but still need limited permissions. Partners must enable two-step authentication to use collaborator access. Put the project end date in your work checklist and remove access on time; inactivity expiry is not a project offboarding process. Sent, accepted, signed in, and able to complete the job are separate results to record.
Verify sign-in and prepare recovery after a lost phone
Owners and people with privileged payment, user-management, or app responsibilities should enable and retest 2FA. Your team can also require secure sign-in for everyone. A compromised lower-privilege login can still give an intruder access to the data and actions it permits. Each person manages authentication for their own Shopify ID; the owner cannot configure another staff member's authenticator or view their recovery codes. Recovery responsibility means knowing who handles recovery and how. It does not mean exposing everyone's codes in one shared record.
Eligible administrators can change a user's Secure sign-in method requirement from their details under Settings > Users. Plus provides an organization-wide requirement for all users. Changing a user from not required to required can sign them out, so check that they are not in the middle of work. Inspect both the requirement and the person's configured method. Removing the requirement does not automatically remove their personal 2FA.
The historical image says Secure sign-in method is not required. It cannot be read as proof that every user has completed authentication. It also shows activity logs and the Collaborators area. The historical Chinese reference is 设置 → 用户 → 安全; use current labels when locating your own settings.
Admin path: Settings > Users > Security

The requirement, log entry, and request-code area identify different checks. This image does not establish active 2FA, controlled recovery codes, or availability of the same organization features in your store.
Have the account holder verify authentication and recovery
Set up the method and sign in again
Where in the UI: Shopify accountSecurity
Open your own account through the store-name or profile entry and go to Security. Under Two-step authentication, complete setup for the chosen authenticator, security key, or other supported method. The refreshed admin can place these entries differently. Prepare a working backup method and recovery codes before signing out and back in during a safe work window.
How to confirm
The account holder completes sign-in with the correct identity and method. Record enabled status and the last retest time; an enabled label alone is insufficient.If it goes wrong
If sign-in fails, pause high-risk work and use the prepared backup method or recovery code. Removing a user and inviting the same email again does not reset that Shopify ID's 2FA.Keep as evidence
Keep status, time, responsibility, and evidence location. Exclude authenticator QR codes, phone numbers, passwords, and verification codes.Store recovery codes and assign custody
Where in the UI: Shopify accountSecurityTwo-step authenticationRecovery methods
The account holder stores recovery codes in a safe, access-controlled place that remains reachable during recovery, such as a controlled password vault. Do not depend on a screenshot on the same phone. Each account has its own codes, and a code works once. While signed in, use Regenerate codes when needed and replace the old stored copies.
How to confirm
Record responsibility and a location reference. Check that losing the phone would still leave an appropriate recovery route. A rehearsal need not expose or consume a real code.If it goes wrong
If both the method and codes are unavailable, use Shopify's identity-verification and account-recovery process. Do not promise its timing or result. Eligible Plus organizations may have additional reset options; the organization owner must check the conditions.Keep as evidence
After recovery, check sign-in, authentication methods, and new-code custody. Replace old copies and record the review time without recording code values.
The record establishes that you arranged and checked recovery. It cannot guarantee immediate access under every future device, email, or platform condition. Include responsibility for the recovery email and authentication device in your own controlled inventory, without exposing actual recovery information in a public tutorial, chat, or lesson record.
Offboard every access path
When a project ends, someone leaves, or a job changes, first name the target, timing, operator, and approver. Staff users, collaborators, device sessions, app/API tokens, and shared secrets are separate paths. Removing one user does not complete the whole review. Before an action affects operations, record dependencies, the recovery method, and who will verify the result.
An API is an interface through which software exchanges data or performs authorized actions with the store; a token is one kind of credential that software uses. A warehouse integration, for example, may read orders through its own app authorization rather than a departing employee's browser login. After removing the person's access, ask which software credentials remain valid, who owns them, and whether they are still needed. One fewer name in Users cannot answer those questions.
I removed the user: has all access stopped?

As text: the whole walk-through
- Removed from the user list First remove the user in Settings > Users; the user account card goes dark.
- Warehouse integration may still read Then ask which software credentials remain valid: a warehouse integration may read orders with its own authorization.
- Collaborator removed A collaborator is a separate path; remove it with Actions > Remove.
- Device cut off Where needed, use Revoke Access on the device or app separately, then check the log.
- Apps and API checked List the apps and API tokens he touched; revoke the ones no longer needed and verify those still running.
- Secrets rotation arranged For secrets that may be shared or exposed, arrange rotation through the platform's process.
- Revocation recorded Record time, target, operator, approver, result and log location, never secret values.
Illustrative: only the five paths the lesson names and its warehouse-integration example; labels follow your store's current screens.
Revoke access and inspect the result
Handle staff and collaborator access first
Where in the UI: SettingsUsersuser details
An eligible person can use Actions > Suspend for temporary staff deactivation, or Actions > Remove and confirmation for permanent removal. Organizations generally use Actions > Remove for collaborators; a non-organization view may show Remove collaborator account. Confirm the target and current screen. Permanent removal cannot be undone; a collaborator needs a new request to return.
How to confirm
Check the user, store, and resulting status. Where needed, handle Revoke Access for a device or application separately, then review permitted access tests and logs. Signing out one device does not close other accounts or API paths.If it goes wrong
Before removing a shared account, arrange appropriate individual access for active staff. If access remains afterward, inspect other users, organization scope, and remaining tokens. Pause access expansion and keep an incident record.Keep as evidence
Keep the revocation time, target, operator, approver, result, and relevant log location. Do not remove a real user merely to reproduce a screenshot.Then review apps, APIs, and shared secrets
List the apps, API tokens, and shared secrets the person could use. Check their remaining purpose, owner, and authorization individually. Revoke unneeded access and arrange rotation of potentially shared or exposed secrets through the relevant platform's process. Check business dependencies first and verify integrations that should keep working; do not uninstall every app indiscriminately.
How to confirm
Give users, collaborators, app/API access, key rotation, and activity review separate checklist items and evidence. Record credential names or references, not secret values.If it goes wrong
If the result is unexpected, the integration owner checks remaining paths and dependencies and follows the recorded recovery plan. Do not assume permanent deletion offers one-click restoration.Keep as evidence
Keep the rotation record, integration checks, log locations, unresolved items, and review date.
Use the following scenarios to turn an exception into a specific check. If a former user still has access, for example, locate the account, organization grant, or token that remains. Clicking a removal button again does not establish that you found the remaining path.
| Situation | Check first | Continue when | If the condition is unmet | Record to retain |
|---|---|---|---|---|
| An invitee cannot see a feature | Job, role, store or organization scope, plan, and resource conditions | The job works while unrelated high-risk access stays off | Repair the missing scope and retest; do not jump to Full permissions | User, role, and allowed/denied test results |
| 2FA fails or a phone is lost | Account status, backup method, and recovery-code responsibility | Sign-in works after recovery and new custody records are checked | Pause high-risk work and use controlled recovery | Recovery owner, retest time, and result |
| Access remains after departure | Other users, collaborators, organization scope, app/API tokens, and shared secrets | Person, token, and log checks each have a result | Close remaining paths, rotate where needed, and retain the incident record | Revocation sheet, rotation record, and logs |
| The matrix has no regular review | Role owner, last review, and exception expiry | Each high-risk exception has an expiry and next review | Pause new access and assign owners and review dates | Matrix version, owner, and next review |
Write the actual result and outstanding work for each applicable case. Keep access expansion paused when an exception has no owner or a permission cannot be explained. Knowing where the control lives does not establish recovery or completed revocation.
If an app, script, or automation invites users, changes permissions, or revokes access, record its input owner, approver, and rollback method. Identify the authorization, recovery, and removal decisions that require human judgment. Pause access expansion if these arrangements are missing. Compare a success message with the intended user, effective permissions, and activity record.
Practise the theme-development decision
Return to the example developer who needs theme access but asks for the owner login and full customer permissions. The question is whether access matches the job. Approved restricted access can cover the theme task. Sharing the owner password makes actions hard to attribute, and a shared administrator leaves no clear individual target for offboarding.
Choose the response before reading the reasons. The recommended choice preserves individual accountability and task scope; selecting it does not invite a person or change Shopify for you.
Choose the developer's access
Self-check not answered
After choosing restricted access, check your own current store. Leave an item unticked when you lack evidence and name the person who will investigate. This checklist records your checks; it does not save Shopify settings or perform sign-in tests.
A full checklist establishes a check record. Also confirm controlled recovery codes, limited external access, and clear revocation responsibility and dates. Checklist color does not establish completed security when identity, recovery, or removal evidence is missing.
Before expanding access
| Done when | Stop if |
|---|---|
The owner identity is controlled and everyone signs in individually. Roles match jobs, privileged sign-in is retested, external access is limited, and recovery and revocation have owners and dates. | Someone shares the owner password, permissions lack a reason, 2FA or recovery is unverified, or offboarding has no owner. |
| Evidence Current user and role records, allowed and denied task tests, sign-in retests, recovery custody, and separate revocation and log results. | |
Keep the access and revocation record
Keep actual observations and unresolved work in a document you control: person and job, roles and stores, approver, 2FA retest, recovery-custody reference, project end date, app/API review, revocation results, and next review. Mark missing information pending with a responsible person instead of describing a plan as completed work.
The form saves automatically in this browser and reuses the decision and checks above. Use redacted practice details, job names, and references to your own records. Exclude passwords, recovery codes, request codes, tokens, real emails, and customer information. Export the record before changing browsers or devices.
What this record establishes
Hold
Make the access decision
Correct shared access first
Some checks remain
Decision and checks recorded
Work it out: which account carries the widest exposure
Four accounts (example data). Rule: read sign-in verification before role scope — a role can be narrowed later, a leaked credential cannot; an account without two-step verification hands its permissions to anyone who has the password.
Role and verification state for four accounts
| Item | Role | Role scope | Two-step verification | Also |
|---|---|---|---|---|
| Account A | Store owner | All permissions | On | Recovery codes stored separately |
| Account B | Support | Orders and customers | Off | Registered with a shared mailbox |
| Account C | Warehouse | Inventory and shipping | On | Own login |
| Account D | Outside designer | Admin | On | Access removed at contract end |
Decide before you read on. Say which account carries the widest exposure, and give your reason.
Answer key: account B is the widest exposure — no two-step verification and a shared mailbox mean anyone holding that password sees orders and customer data, and this kind of leak needs nobody to misbehave. D's role is indeed too broad, yet verification is on and access ends with the contract, which makes it a scope to narrow rather than a door standing open. A and C are sound on both counts. D is the trap: an admin role for a contractor looks the most alarming, but an oversized role needs someone to abuse it while a leaked credential does not.
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- Can several people share one Shopify owner account?
Do not share it. The long-term responsible person controls the owner identity, while others use individual staff or eligible collaborator access. Separate identities make actions attributable and access individually revocable. A lack of regular staff seats on Basic or Starter is not a reason to share the password.
- Are Full permissions the fastest fix?
They may reveal a button while widening customer, payment, user, and app exposure. Check the task, role, store, and plan scope first. For a necessary exception, record the reason, approver, expiry, and retest, then remove it on time.
- What is the difference between a collaborator and a staff user?
The store invites staff within its plan allowance. External Shopify Partners generally request collaborator access, which does not use a regular staff seat. Verify identity and limit permissions for either type, then remove access when the job or project ends. A request code does not replace request review.
- Does everyone need 2FA?
At minimum, owners and privileged users should enable and retest it. A team can require secure sign-in more widely. Each person configures their own method; distinguish individual requirements, Plus organization-wide requirements, and actual personal 2FA. Partners must activate two-step authentication to use collaborator access.
- Is an enabled 2FA label enough?
Prepare the backup method and recovery codes, then sign out and back in during a safe work window. Confirm that the account holder can use the method. Keep recovery codes in a controlled, confidential, reachable location, and exclude code values, authenticator QR codes, and phone numbers from captures and chat.
- Does a developer need customer and order permissions?
Most theme work does not need full customer data. Consider temporary access only for a specific debugging task with a defined data scope, expiry, and approver, then remove it. Theme access should not come bundled with full customer export.
- Does removing a collaborator finish the app and API review?
Users, app/API tokens, shared secrets, and device sessions are separate paths. Check them individually, review relevant activity, and verify integrations that should remain operational. Permanent collaborator removal does not automatically rotate every shared secret.