Getting Started

This chapter is the foundation of the whole course: without a developer account, nothing that follows (certificates, submission, monetization) is possible. After finishing it, you will be able to enroll an account on your own, navigate the App Store Connect interface, and configure least-privilege roles for your team. Getting that foundation right also removes a class of late surprises, because the entity you enroll under and the permissions you hand out are both expensive to change once other people and builds depend on them.

The account type you pick shapes everything downstream, so the chapter starts with the difference between Individual, Organization, and Enterprise accounts and what each one commits you to: whether the App Store listing shows a personal name or a company legal name, whether you can add team members at all, and what paperwork enrollment demands along the way, such as the D-U-N-S number an organization has to obtain before it can be approved. Once the entity question is settled, the enrollment flow itself is mechanical but unforgiving — the details have to match your legal documents exactly, and the waiting period after submission is not optional. From there the chapter turns to the platform you will use every day for the rest of the course, mapping out the top navigation, the app detail page, and how search and filters behave, and then to roles and permissions, where the principle of least privilege decides whether a teammate can only ship builds or can also edit pricing and read financial reports.

By the end of the chapter you should be able to explain the key differences among Individual, Organization, and Enterprise accounts and choose the right one for your situation, complete the enrollment flow yourself including the D-U-N-S step and the waiting period, find Apps, TestFlight, Users and Access, and the financial report entries quickly once you are inside the platform, and assign roles to developers, operations, and finance staff by granting the minimum each of them actually needs. Readers publishing for the first time are best served by working through the material in sequence with a real account open in front of them; publishers who already hold an account can concentrate on the role and permission material and its least-privilege practices; and team leads get the most value by planning member permission boundaries in advance rather than granting access on request after someone asks.