Google Play Target Audience and Content Declaration
How to pick an age group, what triggers the Families Policy and which listing mistakes get apps rejected.
Read the guide →Google Play App Access Instructions for Reviewers
Quick answer App access instructions tell Google how to log in and reach every feature of your app. Give reusable English demo credentials that never expire, work anywhere and skip 2-step verification.
Your app is finished, your testers are ready, and then the review stalls because Google cannot get past your login screen. App access instructions are one of the simplest declarations in Play Console and one of the most common causes of avoidable rejections. This guide explains when you must give Google credentials, how to write instructions a reviewer can follow in two minutes, and how to keep a demo account working for as long as your app is in review.
What are Google Play app access instructions?
App access is a declaration in Play Console, under App content. You tell Google whether any part of your app is restricted and, if it is, how a reviewer can get in. Google's app access help page says you must provide the necessary information for the review team to log in and access all app functionality so the app can be checked for Developer Program policy compliance. It is also one of the prerequisites for the target audience and content section.
When do you need to provide access?
| Your app | Do you need to provide access? |
|---|---|
| No login, everything is open | No. Declare that all functionality is available without restrictions. |
| Requires sign-in | Yes. Provide working credentials. |
| No sign-in but a subscription paywall hides features | Yes. Provide a way to see paid content without paying. |
| Needs a special code, QR code or location | Yes. Provide an alternative that works anywhere. |
| Third-party login (Google, Facebook) | Yes. Provide full account information for a test account. |
What should you provide?
- A demo account with a pre-configured username and password.
- Step-by-step instructions for restricted areas, such as how to reach a screen that needs a certain state.
- A static URL uploaded to Play Console for QR codes, barcodes and other non-alphanumeric access methods.
- Full third-party account details where the login uses an outside account.
- Clear instructions if users create their own password or PIN to reach content.
What rules must the credentials follow?
| Rule | Why |
|---|---|
| Always accessible and reusable | Reviewers may sign in several times, at different times |
| Valid from any location | Reviewers can be anywhere. Geo-gated passwords fail. |
| Work without errors | A failed login blocks the review |
| No one-time passwords or 2-step verification blocking access | Provide credentials that bypass them |
| In English | Provide an English version if your login is in another language |
| Do not expire | Expired passwords can mean the app is rejected |
How do you write instructions a reviewer can follow?
- Say what the app needsOne sentence: Login required. A demo account is provided.
- Give the credentialsUsername and password, in plain text, exactly as typed.
- Explain the pathHow to reach each key feature, in numbered steps.
- Cover special statesIf a feature needs data, say how to create it, or pre-load the demo account.
- Add notes about paid contentSay how the reviewer can see premium screens without paying.
- Test it yourselfLog out and follow your own instructions on a clean device.
A copy-ready template
Template: This app requires sign-in. Demo account email: reviewer@example.com. Password: [password]. Steps: 1) Open the app and tap Sign in. 2) Enter the email and password above. 3) The home screen shows [feature]. 4) To see [premium feature], open Settings > Plan > Reviewer access. The account does not use 2-step verification and does not expire.
Use a real address you control for the demo account and a unique password, never a password you use elsewhere. Rotate it after review if you wish, but only after the app is approved, and never while the app is in review.
Which mistakes cause rejection?
- Credentials that expire, or a demo account that requires a code sent to your phone.
- Instructions that assume the reviewer knows your app.
- A demo account with no data, so the main screens look empty.
- A login that works only from your country.
- Leaving the declaration saying no login is needed, when there is one.
- Forgetting about the closed test. Reviewers of your production application may look at the same access information.
If your app is rejected for access reasons, fix the credentials and resubmit. See app rejection reasons and fixes and how to release the updated version.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: Provide information for app access
- Google Play Console Help: Target audience and app content
What should you provide for different kinds of apps?
| App type | What to provide | Common trap |
|---|---|---|
| Email and password login | A demo account with data already in it | Empty account, so main screens look blank |
| Login with Google or Facebook | Full details for a test account of that provider, with simple instructions | Test account asks for phone verification |
| Phone-number login with SMS codes | Credentials that bypass the code, or a fixed test number if your system supports it | Reviewers cannot receive SMS |
| Subscription paywall | A way to open premium features without paying | Reviewer is stuck at the payment screen |
| Dating or social app | Two demo accounts so the reviewer can see interaction | Accounts cannot see each other |
| Employee or school app | A sandbox account and a short note on what each role sees | Real company data in the demo |
Keep your demo account safe
- Use a dedicated account with no real personal data.
- Use a strong password you do not reuse anywhere.
- Disable anything that could send real emails, payments or messages from the demo account.
- Keep it active for as long as the app is in review and after, because later updates need review too. See how to update an app on Google Play.
Final check before submitting
| Check | Done? |
|---|---|
| I logged in on a clean phone using only the text I gave Google | ☐ |
| The account works from another country or network | ☐ |
| No one-time passwords or 2-step verification in the way | ☐ |
| Instructions are in English | ☐ |
| Premium content opens without payment | ☐ |
Frequently asked questions
When do I have to give Google login details?
When your app requires sign-in. Google also says that if an app has no sign-in but features or content sit behind a subscription paywall, you must supply access so reviewers can explore it without paying.
What if my app uses one-time passwords or 2-step verification?
Supply reusable credentials that bypass those steps, as Google requires credentials to be reusable and to work without errors.
Can I give credentials in another language?
Credentials must be in English. If your normal login is in another language, provide an English version.
What if my login is location-based?
Provide credentials that work regardless of where the reviewer is. Google says credentials must be valid from any location.
What happens if my demo password expires?
Google says that if the password expires, the team may not be able to review the app and it may be rejected.
How do I share a QR code or barcode?
Google says non-alphanumeric access methods such as QR codes or barcodes need a static URL uploaded to Play Console.
