Google Play Console Settings for Closed Testing: Every Setting Explained

Google Play Console has dozens of settings, and several of them directly determine whether your testers can access your app — or whether your production access application gets approved. These are the settings that matter most, in the order you will encounter them.

1. Developer Account Setup

Where: Settings > Developer account > Account details

Before creating a testing track, confirm your account type. If “Account type” shows “Personal” and you have never published a production app, the Closed Testing requirement applies to you.

Check: Your account identity verification is complete (required during account creation). An unverified account cannot publish testing tracks.

2. App Setup: Privacy Policy

Where: Policy > App content > Privacy policy

Google requires a privacy policy URL in your store listing before your app can be reviewed for any testing track. Without it, your Closed Testing track submission will be rejected during Google’s app review.

What to do: Host a privacy policy page on your website or use a free privacy policy generator. The URL must be accessible and the policy must cover:

• What data your app collects
• How data is used
• Third-party data sharing (if any)
• User rights regarding their data

3. Closed Testing Track Creation

Where: Testing > Closed testing > Create track

Track name: Choose something descriptive (“Beta 1.0,” “Pre-release v1”). This name is only visible to you in the Console.

Countries / regions: This is the setting that causes the most tester access failures. When you create a track, the default country selection may be empty or limited. You must explicitly add every country where your testers are located. If a tester is in Brazil and Brazil is not in your country list, they will see “App not available in your country” when clicking the opt-in link.

To add countries: Manage track > Countries / regions > Add countries / regions. Add all countries where testers live. If using a global testing service like TesterBee, add major countries across every continent.

4. Tester Management

Where: Testing > Closed testing > Manage track > Testers

You have three options for managing who can access your app:

Email list: You manually add tester email addresses, or testers opt in using a shared link. This is the simplest method for first-time setups. Google generates a unique opt-in URL — anyone with the link can opt in and install. You can also add individual emails if you prefer invitation-only.

Google Groups: You manage a Google Group email address. Anyone in the group can access the app. Best if you already use Google Groups for team management.

Which to choose: Email list is simpler and recommended for most developers. The opt-in link method means you do not need to collect and enter 12 individual email addresses — you share one link and testers opt in themselves.

5. App Bundle Upload

Where: Testing > Closed testing > Manage track > App bundles

Upload your .aab file. Requirements:

• Signed with a release keystore (not debug)
• Target API level meets Google’s current minimum (API 34+ as of 2025)
• Version code is higher than any previous upload to this track

If using Google Play App Signing, Google manages the signing key after upload. Your upload key is used only for authentication, not for the final APK signature.

6. Rollout Management

Where: Testing > Closed testing > Manage track > Rollout

Start rollout: Makes your track live. The 14-day clock begins when the track reaches “Available” status — not when you click “Start rollout.” Google reviews your app first, which typically takes a few hours. The clock starts after the review passes.

Pause track: Pausing stops new installs and may affect the 14-day count. Do not pause your track during the 14-day period unless you have a critical issue that requires taking the app offline.

Resume track: Resuming after a pause does not reset the clock, but the paused days do not count toward the 14-day requirement.

7. Statistics & Monitoring

Where: Testing > Closed testing > Statistics

During testing, monitor:

• Installs: Current install count — stay above 12
• Uninstalls: If uninstalls are rising, a tester or testers are leaving — replace them
• Crashes: Crash rate should stay below 1%. A high crash rate signals poor app quality.

Also check Android Vitals (Quality > Android vitals > Overview) for:

• Crash rate
• ANR (Application Not Responding) rate
• These metrics are part of what Google’s review team evaluates.

8. Production Access Application

Where: Production access (appears after the 14-day Closed Testing requirement is met)

After completing 14 days of testing, the “Production access” option becomes available. This is where you submit the questionnaire. See our production access guide for detailed question-by-question guidance.

Settings Developers Miss

These are the settings that cause the most support requests:

Country availability not set: Your opt-in link works, but testers in certain countries cannot access the app. Always check country settings before sharing your link.

Track not rolled out: You uploaded a bundle, configured testers, and shared the link — but never clicked “Start rollout.” The 14-day clock has not started. Your track status should show “Available,” not “Draft” or “Ready to publish.”

App review pending: After starting rollout, your app enters Google’s review queue. This can take several hours. The clock starts after the review passes. Do not tell testers the testing period has begun until the track shows “Available.”

Privacy policy missing or inaccessible: Your track submission is rejected during review. The rejection message will state “Privacy policy” as the reason. Add a valid privacy policy URL and resubmit.

Frequently Asked Questions

Can I edit my app during Closed Testing?

Yes. You can upload new app bundles to the Closed Testing track at any time. Testers will receive the update through the Play Store like any other app update. Deploying at least one update during testing is recommended.

How do I know if my track is live?

Check Testing > Closed Testing. The track status should show “Available” with a green indicator. If it shows “In review,” Google is still processing. If it shows “Draft,” you have not started the rollout.

Can I change tester emails after testing begins?

Yes. You can add or remove tester emails at any time. New testers can join mid-cycle.

What if I need to change the app name or description?

You can edit your store listing at any time without affecting the testing track. Store listing changes go through a separate review process.