Do I need to fill in App access if my app doesn't require a login?

If every feature can be used without logging in, just declare that. But if there are features or content behind a subscription paywall even without a login, Google's documentation says you should explain how the review team can get to them.

Can I give them a real user's account?

It's safer to create a separate demo account just for review. The documentation says login credentials must be reusable and valid at all times, so an account whose password gets changed or that gets locked will block the review.

What if my app uses phone verification (OTP)?

Google's documentation says that if your app requires 2-step verification codes or one-time passwords, you should provide reusable login credentials that bypass that step. Set up your review account so it skips verification.

Can I write the login details in a language other than English?

The documentation says login details must be provided in English. Write any instructions you include with the username and password in English too.

I changed the password but didn't update Play Console.

Update it right away. Google's documentation says that if the password you provided expires, your app can't be reviewed and may be rejected.

← Blog

Requirements

Google Play Console App access: how to provide login details for review

If your app requires a login, you must provide login details in Play Console so Google's review team can access every feature. Based on Google's Help Center documentation, we cover when it's needed, what the credentials must meet (reusable, location, 2-step verification, English, QR codes), and what happens if the password expires.

Last checked Oct 14, 2026.

1. What App access is

When Google reviews your app, reviewers actually use its features. But if your app requires a login, the reviewer gets stuck on the first screen. That’s why the Play Console Help Center article says you must provide, in Play Console, the information the Google team needs to log in and access all of your app’s features. You enter this information in the App access section of your app setup.

All features are available without logging in — declare that.
A login is required, or some features are restricted — provide a review username and password, plus instructions for getting in.
No login, but some features are behind a subscription paywall — explain how to get to those features.

2. What your login credentials must meet

The documentation sets out six conditions. If even one is off, the reviewer can’t get into your app.

They must work anytime, anywhere, and more than once. They must always be accessible regardless of the user’s location, reusable, and valid. A login that only works from IP addresses in one country may be blocked.
They must bypass 2-step verification and one-time passwords. The reviewer can’t receive a code sent to your phone.
Write them in English. Both the username and password and any instructions.
If users log in with a QR code or barcode, create a static URL and upload it to Play Console.
If users have to set their own passcode, such as a PIN, clearly explain how to set it.
They must not expire. If the password expires, your app can’t be reviewed and may be rejected.

3. Tips for setting up a review account

Create a demo account just for review rather than using a real user's account. Make sure its password never changes and it never gets deactivated.
Load the demo account with enough sample data to show your app's main features right away. If the reviewer only sees empty screens, they can't check the features.
If your app has phone or email verification, let the demo account skip that step.
If your service makes passwords expire after a set period, exempt the demo account.
If an update changes how users log in, update the details in Play Console at the same time.

Closed testing releases go through review too. If review hasn’t finished after several days, check your login details first (when closed testing is stuck in review).

4. The same thing happens to your testers

Wherever the reviewer gets stuck, your closed testing testers get stuck too. If sign-up is difficult or the app stalls at a verification step, testers never reach the features, and there’s no sign that the app was actually used during the test. That’s one of the common reasons a production access request comes back with “testers were not engaged with your app” (the testers-not-engaged rejection). Give your testers an easy way to sign up, or a test account they can use right away.

Along with App access, another app setup item people often get stuck on is the privacy policy.

Frequently asked questions

Do I need to fill in App access if my app doesn't require a login?: If every feature can be used without logging in, just declare that. But if there are features or content behind a subscription paywall even without a login, Google's documentation says you should explain how the review team can get to them.
Can I give them a real user's account?: It's safer to create a separate demo account just for review. The documentation says login credentials must be reusable and valid at all times, so an account whose password gets changed or that gets locked will block the review.
What if my app uses phone verification (OTP)?: Google's documentation says that if your app requires 2-step verification codes or one-time passwords, you should provide reusable login credentials that bypass that step. Set up your review account so it skips verification.
Can I write the login details in a language other than English?: The documentation says login details must be provided in English. Write any instructions you include with the username and password in English too.
I changed the password but didn't update Play Console.: Update it right away. Google's documentation says that if the password you provided expires, your app can't be reviewed and may be rejected.

Meet the requirement without recruiting testers

DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.

Check installability See how it works