Protect the accounts that control your app
Use passkeys on every account that can change your app's code, configuration, infrastructure, or DNS, and multi-factor authentication where passkeys aren't supported. Remove access as soon as people no longer need it.
Any account that can change your app's code, configuration, infrastructure, or DNS can be used to put code on every store that uses your app, without a vulnerability in the code.
Passkeys and security keys resist phishing, because they work only on the real site that they were created for. Other multi-factor methods are weaker, but still far stronger than a password alone.
- Turn on two-step authentication for every Shopify account in your Partner organization.
- On your hosting, cloud, DNS, CDN, source control, CI/CD, package registry, error tracking, and email accounts, use passkeys wherever the service supports them. Email matters because it can reset the passwords for everything else.
- Register at least two passkeys for each account, such as one on your laptop and one on a security key, and keep recovery codes offline, so a lost device doesn't lock you out.
- Where a service doesn't support passkeys, turn on multi-factor authentication, and enforce it for your whole organization if the service lets you.
- Keep multi-factor authentication on for any account that still accepts a password. Adding a passkey doesn't always turn off password sign-in.
Choose the strongest method that each service offers:
| Method | Resists phishing | Notes |
|---|---|---|
| Passkey | Yes | Unlocks with a fingerprint, face, or device PIN. |
| Security key | Yes | A separate physical device. Suits administrator accounts. |
| Authenticator app | No | A fake sign-in page can capture the code. |
| SMS or email code | No | Exposed to SIM swaps and interception. Use only when nothing else is available. |
- Give each person their own account with only the access that they need. Don't share logins.
- Remove access as soon as someone leaves or changes roles, including Partner organization access, store collaborator access, cloud and repository access, and any API keys or tokens that they created.
- Keep your emergency developer contact current in Organization settings in the Dev Dashboard, so Shopify can reach you quickly about a security issue.
Anchor to VerifyVerify
No app security check covers this practice, because it lives outside your code. Review it when people join or leave your team: check that each account uses a passkey or security key where the service supports one, and the strongest multi-factor method that the service offers everywhere else, including any password sign-in that remains.