Internal testing is for the team
Internal testers are App Store Connect users with appropriate access to your content. Confirm team membership and app permissions before assigning a processed build to a testing group. Do not grant customer accounts developer-console privileges merely to let them test. Using TestFlight does not require giving ordinary testers app-management access.
External testing reaches other users
Customers and public beta participants normally belong in external testing. Create a group, add a build, provide test information and invite users through Apple’s workflow. External builds may need Beta App Review: the first build added to a group enters the relevant review flow, while later builds may not require a full review. Do not promise immediate installation after upload.
Beta approval is not public release
For a public App Store version, prepare version information, choose a build and submit for review separately. Beta App Review and App Review are different stages. An approved test build does not automatically approve the store release. Existing testers may continue using invited builds after launch rather than switching automatically to the public app.
Check the tester experience
Verify invitations, groups, available builds and device compatibility with a target tester account. A TestFlight build can be tested for up to 90 days; expiry affects installation and continued testing. It is not permanent distribution. Record build numbers, the testing end plan, the public-release channel and where testers should send feedback.