Skip to main content

Studio app setup

Own your app-store accounts. ClassFlow handles the release workflow.

Create the accounts in your studio's legal name, then add the required IDs and credential files inside ClassFlow. Keep ownership, billing, agreements, and store access with your business.

Before you start

  • Use a studio-controlled email address and payment method. Do not create the account under an employee or agency identity.
  • Use the studio legal entity and D-U-N-S or business-verification details exactly as registered.
  • Choose the final app name and identifier before creating store records. Identifiers are difficult or impossible to change later.
  • Finish all current agreements, tax, banking, identity, and phone-verification prompts in each provider console.

iPhone and iPad

Apple Developer

1. Enroll as an organization

  • Enroll the studio in the Apple Developer Program as an Organization, not as an individual contractor.
  • The studio owner should be the Account Holder and keep access to the Apple ID, trusted phone number, and renewal payment method.
  • Wait until enrollment is active before creating signing assets or the App Store record.
Open Apple enrollment

2. Create the app identity

  • Create an explicit App ID for the bundle ID shown in your ClassFlow app configuration.
  • Enable Push Notifications and the capabilities ClassFlow identifies during onboarding.
  • Create an Apple Pay merchant identifier if the app will offer Apple Pay.
  • Create the app record in App Store Connect and copy its numeric Apple ID into ClassFlow.

3. Create release credentials

  • Create an App Store Connect API key with only the access needed to manage and upload this studio app. Save the issuer ID, key ID, and downloaded .p8 file.
  • Create an Apple Distribution certificate and export it as a password-protected .p12 file.
  • Create an App Store distribution provisioning profile for the exact bundle ID.
  • Create an APNs key when push notifications are enabled and save its key ID and .p8 file.

Android

Google Play

1. Create and verify the organization account

  • Create the Play Console account using the studio organization and a studio-controlled Google account.
  • Complete organization identity, contact, phone, and website verification plus the developer registration payment.
  • Keep the account owner role with the studio. Additional users should receive the minimum permissions needed for their job.
Open Play Console signup

2. Create the app and API access

  • Create the app using the Android package name shown in ClassFlow and complete the required app-content declarations.
  • Create a dedicated Google Cloud service account, link it to Play Console, and grant access only to this app and its releases.
  • Download the service-account JSON once and keep it private until it is uploaded to ClassFlow.

3. Create the upload key

  • Create a dedicated upload keystore and alias for this studio app. Do not reuse another studio app key.
  • Keep the keystore, alias, keystore password, and key password together in the studio release record.
  • Use Play App Signing for the production signing key; the local release workflow uses the studio upload key.

Secure handoff

Upload credentials inside ClassFlow

Do not email keys, passwords, certificates, or JSON files. ClassFlow stores credential values encrypted and only materializes them for the selected studio's local release.

ClassFlow validates before release

Save the account, run Test connection, fix every blocker, and approve the exact version and target. Native build and store commands run only on the authorized local release Mac.

Need help? Send non-secret screenshots of the blocker to support@getclassflow.com. Keep every credential file and password inside the secure configuration screen.