Skip to content

Guides

Google Play App Access Instructions for a Website App: What to Enter (2026)

Reviewers must be able to sign in to every restricted part of your app. Here is what to enter under Sign-in details, how to handle Google-only logins in a WebView app, and how to resubmit.

Updated 12 min read

Google Play app access instructions are the login details and notes you add in Play Console, under App content, then Sign-in details, so a reviewer can open every restricted part of your app. For an app built from a website, that means a dedicated test account that works inside the installed app, never expires, and does not ask for a code sent to your phone. Add it before you submit: a reviewer who cannot get in will reject the update, even if everything else is fine.

Older rejection emails and forum threads call this section "App access". Google's current help page labels it Sign-in details. It is the same form, and the details below were checked against Google's pages in November 2026.

Instruction sets

5

allowed per app

Review time

Hours to 7 days

longer in exceptional cases

Language

English

required for credentials

Where do I enter app access instructions in Play Console?

  1. 1Open Play Console, select your app, then go to Monitor and improve, Policy and programs, App content.
  2. 2Under Sign-in details, select Start. If you filled it in before, you will see Manage instead.
  3. 3Click Add new instructions and enter the access details a reviewer needs.
  4. 4Use the Any other instructions field for anything unusual. Google names one-time passwords, multi-factor authentication and logins with more than two fields as examples.
  5. 5Save. You can add up to five sets of instructions, which helps if your app has separate customer and admin areas.

These steps follow Google's Prepare your app for review page.

Do I need sign-in details if my app has no login?

Only if part of it is restricted. Google asks for access details when the app, or part of it, is limited by login credentials, memberships, location or another form of authentication. One case surprises people: an app with no login at all, but content behind a subscription paywall, still needs instructions that let the reviewer get past the paywall for free. If everything is open to anyone, there is nothing to declare here, but your privacy policy and Data safety form still apply.

What does Google require from the credentials I give?

  • Always available and reusable. The details must work for any reviewer, at any time, regardless of location.
  • Maintained without error. If your app normally asks for a 2-step code or one-time password, provide reusable credentials that bypass it. Google warns that an expired password can stop the review and lead to rejection.
  • In English, even if your app normally uses another language.
  • Static, if not text. For a QR code or barcode, generate a static URL and upload it.
  • Clear steps where users set their own password or PIN to reach content.
  • Location-proof. If your app uses a location-dependent login, provide credentials that work from anywhere.

All six come from Google's sign-in details requirements. Google's Play Console Requirements policy backs them up: providing an active demo account and login information is on its list of things to do before you submit, and submitting outdated sign-in details is on its list of things not to do.

What should I enter for each type of website login?

What to give the reviewer, by login type (our summary of Google's requirements, November 2026)
Your website's loginWhat the reviewer needsWhat to write in the instructions
Email and passwordA dedicated test account with sample data loadedUsername, password and the screen to start on. Do not change the password after you submit.
Email link or one-time codeA review account that skips the codeReusable credentials that bypass the code, plus a line in Any other instructions saying so.
Sign in with Google or Facebook onlyA way in that works inside the appAccount details and exact steps, plus an email and password route if the app cannot complete the social login (see below).
Membership or paid content, no loginFree access to the gated contentInstructions or access details that unlock the content at no charge.
Location-restricted accessA login that works from any countryCredentials that are valid regardless of location.
QR code or barcode loginA static image URLThe uploaded URL and the steps for scanning it.

Does my review account need to reach report and block tools?

If your website lets users post content that other users can see, yes, in practice. Google's User Generated Content policy asks for in-app tools to report content and users and to block users, and the review account is how a reviewer finds them. In a public Discourse thread, a consultant whose client passed a UGC review advised setting the forum's minimum trust level to flag posts to 0, so that Google's test team can see the flag feature (source thread). Our inference is that the same applies to any site: create the review account as a brand-new member, then check that it can report a post and block a user. The full rules are in our guide to Google Play's UGC policy for website apps.

What if my website only offers Sign in with Google?

This is where apps built from websites differ from ordinary native apps. Google's OAuth 2.0 policies, last modified August 5, 2026, say a developer must not send a Google authorization request to an embedded user-agent under the developer's control. That wording describes a WebView inside your own app, and developers report the result as a rejected sign-in: the Google button that works on your website fails in the app with the 403 disallowed_useragent error. We cover the causes and the alternatives in the Google sign-in WebView error guide.

Handing the reviewer a Google account does not fix this, because the reviewer hits the same block. Our recommendation is an inference from the two policies, not something Google states on the sign-in details page: add an email and password option to your site, create a review account on it, and put those credentials in Sign-in details. Then install your release build on a clean phone and follow only the instructions you wrote.

How do I fix a rejection for missing login credentials?

  1. 1

    Read the notice

    Open Policy status in Play Console and note the policy and the app version. Google's notice says the previous version stays available when an update is rejected.

  2. 2

    Fix the review account

    Create or reset a dedicated account for reviewers. Turn off two-step codes and password expiry for it.

  3. 3

    Test it in the app

    Install the release build on a clean phone and sign in using only the text you will give Google.

  4. 4

    Update Sign-in details

    Open App content, then Sign-in details, then Manage. Edit the instructions and save.

  5. 5

    Send for review

    Go to Publishing overview, find your changes and click Send for review. After a rejection, changes are not sent automatically.

Google says you can complete these steps without contacting or waiting for a reply from the policy support team. Processing can take a few hours or up to seven days, so Google recommends leaving a buffer of at least a week before any launch date. For the other reasons reviewers turn apps down, see why Google Play rejects WebView apps, and for the full submission process, how to publish an app on Google Play.

Frequently asked questions

Do I have to give Google Play a test account for my app?
Yes, if your app or part of it is restricted by login credentials, memberships, location or another form of authentication. Google also asks for access instructions when an app has no login but puts content behind a subscription paywall.
Can I use a Google account as the review login for a website app?
Google says to provide all account details and clear instructions for sign-in with Google or Facebook. But Google's OAuth policy bars Google sign-in requests in embedded browsers a developer controls, which describes a WebView. Our recommendation is to add an email and password route for the review account.
What if my login sends a one-time code?
Provide reusable credentials that bypass the code, and say so in the Any other instructions field. Google warns that an expired or code-dependent login can stop the review and lead to rejection.
How many sets of sign-in instructions can I add?
Up to five. That is useful if your app has different areas, such as a customer view and an admin view.
Does my review account need to see report and block buttons?
If your site hosts user posts, yes. Google's UGC policy asks for in-app reporting and blocking, and reviewers use the account you supply to look for them. Make the account a new, low-privilege member and check that those controls are visible to it.
Do I need to contact Google after fixing my sign-in details?
No. Google says you can update Sign-in details, save, and click Send for review on the Publishing overview page without contacting or waiting for the policy support team.
Will a rejected update take my live app down?
Google's rejection notice says that if you submitted an update, the previous version of your app stays available on Google Play. Suspensions and removals are different and more serious.