Private distribution App Review checklist for Business and School Manager
Private distribution is not simply a hidden public app. The distribution method, organization availability, pricing, review account, and support model need to be correct before approval.
Choose private distribution only when the app should be available through Apple Business or School Manager to specified organizations. Apple says App Store Connect supports public distribution and private distribution, and once an app is approved the distribution method cannot be changed without creating a new app record except for public-to-unlisted changes. AppReviewReady interpretation: treat distribution method as a launch-critical architecture decision.
Choose public, unlisted, or private before the first approval
Private distribution should be selected when the app is for specific businesses or educational organizations rather than the public App Store. If the team is unsure, pause before creating release dependencies around the wrong method.
Because changing between public and private distribution generally requires a new app record and resubmission after approval, the decision affects bundle planning, customer onboarding, support, and contracts.
Verify organization identifiers and availability
- Collect the correct Apple Business or School Manager organization details before submission.
- Confirm whether the app is free, paid, discounted for education, or contract-priced.
- Check countries or regions for every organization that should receive the app.
- Prepare a support path for buyers who cannot see the app after approval.
- Keep internal names and customer names out of public metadata when the app is private.
Make private features reviewable
App Review still needs a working build, credentials, sample organization state, and access to the core workflow. Do not assume that a private audience lets you skip demo data or hide unfinished screens.
AppReviewReady interpretation: provide a neutral review organization or sample tenant that demonstrates the workflow without exposing a real customer's confidential data.
Prepare buyer operations
- Confirm who inside the customer organization buys or assigns the app.
- Test redemption, managed distribution, sign-in, and role assignment with a non-production tenant.
- Document how updates, support, incident notices, and account deletion requests are handled.
- Verify pricing, availability, and organization restrictions before publicizing launch to the customer.
- Keep a rollback plan if the wrong organization or price is configured.
Write private distribution review notes
The note should make the private app feel complete and testable. A reviewer should not need access to a real customer contract to understand the product.
Keep a customer-change process for adding or removing organizations after launch. A private app can still create support and compliance issues if pricing, regions, or organization IDs are changed without release-owner review.
For education customers, confirm whether student data, child privacy, and managed device assumptions are reflected in the privacy policy and support workflow.
Private distribution review: Distribution method: [private] Target organizations: [sample or IDs] Review tenant/account: [details] Core workflow: [steps] Pricing/availability: [summary] Support owner: [contact] Confidential customer data: [none in review tenant]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check private app readiness
Review distribution method, organization access, pricing, and review tenant setup.
Open the tool