Attendee App: App Store Access Requirements

To publish a white-labeled Attendee App on the Apple App Store, getregistered needs App Manager access, with Access to Certificates, Identifiers & Profiles, to your organization's Apple Developer account, granted to [email protected]. We never need your passwords or two-factor codes.

That user also needs the Generate Individual API Keys permission, so our build pipeline can upload builds automatically. We create the key ourselves; you don't need to generate or send us anything.

This article is for the IT or developer-account team. Branding assets and store listing copy are covered separately in Attendee App Branding Requirements.

Summary of steps

Check your Apple Developer account is enrolled as an organization and your Account Holder has accepted Apple's latest agreements. (Account Holder)
Invite [email protected] in App Store Connect as an App Manager, with Access to Certificates, Identifiers & Profiles and Generate Individual API Keys ticked. (Account Holder or Admin)
Let us know it's done. We then build, test and submit the app to Apple for review on your behalf.
Forward any emails from Apple about the app to your getregistered contact.

The sections below explain each step in detail.

In this article

Why Apple needs the app in your account
Before getting started
What we need
How to invite getregistered
What we do with this access
Google Play
Frequently asked questions

Why Apple needs the app in your account

Apple will not approve a white-labeled app submitted through getregistered's own developer account. Its App Review Guidelines (section 4.2.6) reject apps built from a template or app platform unless they are submitted directly by the organization that owns the content — in this case, you.

So the app must be published from your Apple Developer account and listed on the App Store under your organization's name. getregistered handles the build, signing, upload and review process; Apple only requires that it happens inside your account.

Before getting started

Your account must be enrolled as an organization, not an individual. Individual accounts cannot grant access to Certificates, Identifiers & Profiles, and the app would be listed under a person's name rather than your company's.
Organization enrollment requires a D-U-N-S number and a person with legal authority to sign Apple's agreements. If you are not yet enrolled, start now: verification can take anywhere from a few days to a few weeks. See Apple Developer Program enrollment.
Your Account Holder must have accepted Apple's latest agreements. Apple blocks uploads and submissions until any updated terms are accepted, and only the Account Holder can do this.
Grant access early. We need access at least three weeks before your target launch date, so there is time to prepare, test and upload the first build and get it through App Store review. Please grant access as soon as your project is confirmed.

What we need

An invitation for one user in App Store Connect, set up as below. We do not need your credentials — the invitation gives our team its own login to your account.

Setting	Value
First name	Apps
Last name	Manager
Email	[email protected]
Role	App Manager (Admin also works)
Additional resources	Access to Certificates, Identifiers & Profiles; Generate Individual API Keys

Why Certificates, Identifiers & Profiles? This permission lets us create the app's bundle ID, signing certificates and provisioning profiles. Without it we cannot sign builds, and you would need to generate and send us these files manually for every release.

Why Generate Individual API Keys? Our build pipeline signs in to App Store Connect with an API key rather than a person's login. This permission lets us create that key under our own user, so you don't need to generate or send us one. The key only ever has the same access as that user.

How to invite getregistered

This must be done by your Account Holder or a user with the Admin role. It takes about two minutes.

Sign in to App Store Connect.
Open Users and Access.
Click the + button next to People.
Enter the name and email address from the table above.
Under Roles, select App Manager. Marketing, Developer and Create Apps are ticked automatically.
Under Additional Resources, tick Access to Certificates, Identifiers & Profiles (leave Access to Cloud Managed Distribution Certificate ticked) and Generate Individual API Keys.
Click Next, then Invite.
Let your getregistered contact know the invitation has been sent. We will accept it, usually the same business day.

What we do with this access

Once access is granted, getregistered handles the full submission process inside your account.

We will:

Create the app record, bundle ID, signing certificates and provisioning profiles
Upload builds and test them through TestFlight
Complete the store listing using the assets from the branding article
Submit the app for review and respond to any questions from Apple
Release updates when needed

We will not:

Touch any other app in your account
Change users, agreements, tax, banking or payment settings
Set a price — the app is free to download

Apple sometimes emails the Account Holder directly about the account or the app. Please forward anything relating to the Attendee App to your getregistered contact.

Google Play

No action is needed from your IT team. Google does not have Apple's restriction on white-labeled apps, so we publish the Android app through getregistered's own Google Play developer account. The app name, icon and listing still use your branding; the developer name shown on the listing is getregistered.

If your organization requires the Android app to be published under your own Google Play account, let us know at the start of the project.

Frequently asked questions

Do you need our Apple ID password or two-factor codes? No. The invitation creates a separate login for getregistered. Never send us your credentials.

Do we need to generate an API key for you? No. With Generate Individual API Keys enabled, we create our own key under the getregistered user. It has the same access as that user, and removing the user stops the key working.

Can we give you the Developer role instead of App Manager? The Developer role can upload builds but cannot edit the store listing or submit the app for review, so we would need your team to complete those steps for every release. App Manager avoids that back-and-forth.

We don't have an Apple Developer account yet. What now? Enroll as an organization at developer.apple.com/programs/enroll. You will need a D-U-N-S number and must pay Apple's annual membership fee. Tell us as soon as you start, because enrollment time affects the launch date.

Can we remove your access after the event? Yes. We recommend keeping it in place until your event has finished, so we can ship fixes or updates quickly. If you plan to keep the app live afterwards, talk to us before removing access.

What happens if our Apple Developer membership lapses? Apple removes your apps from the App Store when membership expires. Make sure renewal covers the period the app needs to be available.

Who do we contact with questions? Your getregistered project contact, or [email protected]. We are happy to join a short call with your IT team to walk through the setup.