App Store Connect Sign-In Requirements Explained

What are the current Apple Developer account sign-in requirements for App Store Connect

App Store Connect requires sign-in with an Apple Account that has two-factor or two-step verification enabled. The Account Holder uses the Apple Account tied to the program membership, and every App Store Connect user must meet the verification requirement before they can sign in.

The Account Holder is the first account that can access App Store Connect for a new team. Apple’s workflow page says that initially only the Account Holder can sign in with the Apple Account associated with the Apple Developer Program membership. After that, the Account Holder can invite additional users in Users and Access.

For the Account Holder, Apple requires two-factor authentication. For all App Store Connect users, Apple allows either two-factor authentication or two-step verification. That requirement is on Apple’s App Store Connect help pages, and it is separate from whether the person is enrolled as an individual or as an organization.

The part people get wrong is assuming any Apple login is enough. It is not. A regular Apple Account without two-factor or two-step verification will not satisfy App Store Connect sign-in requirements. If the account is already enrolled but verification is off, the fix is to enable verification on that Apple Account before trying again.

Apple also expects the Apple Account details tied to the developer profile to be current. On enrollment and account management pages, Apple calls out valid contact information, trusted phone numbers, and trusted devices. That matters because sign-in and security checks rely on those recovery paths when a code is needed.

If you are using the Apple Developer website, the same Apple Account is used to reach developer resources, but App Store Connect has the stricter sign-in rule. The website itself can be accessed with the Apple Account, while App Store Connect requires the verification layer before access is allowed.

If you are setting this up for a team, start with the Account Holder account first, confirm verification is enabled, and then add the rest of the team in App Store Connect. Apple’s role model lets one person control membership duties, legal agreements, and the first App Store Connect access path.

If you are working through DevConnect, the practical sequence is the same: use the account that owns the membership, confirm verification is active, then invite the people who need App Store Connect access. DevConnect does not change Apple’s rule, it just helps you coordinate testing work on devconnectplatform.com.

When sign-in fails, the cause is usually one of three things. The account is not the Account Holder, verification is not enabled, or the Apple Account details are stale. Apple’s help pages point to the required verification settings, so the clean fix is to update the Apple Account first, then try App Store Connect again.

For a solo developer, the practical minimum is simple: one Apple Account, two-factor or two-step verification turned on, and the same account used for the program membership and App Store Connect. For a company team, the Account Holder signs in first, then other users are added afterward through roles and invitations.

The inconvenient part is that there is no shortcut around verification. If a teammate can sign into iCloud but has not enabled two-factor or two-step verification, that person still cannot sign into App Store Connect. If the Account Holder has not enabled two-factor authentication, they cannot complete the App Store Connect flow either.

One more thing gets mixed up often: App Store Connect sign-in is not the same as TestFlight tester access. App Store Connect is for developers and team members managing apps, agreements, tax, banking, and submissions. TestFlight is for beta distribution, and its tester rules are separate from the developer sign-in rules.

A concrete example helps. If an agency sets up an app for a client, the client’s Account Holder Apple Account should be verified first. The agency can then be added as users in App Store Connect, but their own Apple Accounts still need two-factor or two-step verification before they can log in.

The safe checklist is short. Use the Apple Account tied to the membership, enable two-factor or two-step verification, keep trusted contact information current, and make sure the Account Holder can get in before anyone else. That is the current sign-in requirement Apple documents for App Store Connect.