Google Play Reviewer App Access Instructions Checklist

A release can work perfectly for the development team but fail when a reviewer cannot reach a protected screen. Google Play’s App content workflow provides a place for restricted-app access instructions. The useful work is verifying that the instructions match the candidate release—not copying credentials into a public tool.

What matters

Google Play’s App content section lets developers provide special instructions for accessing restricted parts of an app.
Instructions must describe the actual review path for the candidate release, especially when login, enrollment or access restrictions have changed.
A public comparison website should never ask for passwords, one-time codes or private reviewer credentials.

Step-by-step investigation

1. Map locked screensList any features reviewers must log in, subscribe, activate or otherwise unlock to inspect.

2. Compare access flow changesCheck whether the candidate build added login requirements, regional restrictions, OTP flows, permissions or other new gates.

3. Verify private instructions in ConsoleIn Play Console App content, check that reviewer instructions are current and sufficient for the new release. Do not paste confidential details here.

4. Test from a fresh stateUse a clean test device or profile, and follow the instructions as someone unfamiliar with the project would.

5. Keep access evidence privateRecord whether instructions exist and have been tested, without putting secrets into the public report.

A worked example (synthetic)

Example: login gate added

Previously accepted release: no login required. Candidate: login required. The supplied snapshot says reviewer instructions are missing. This is a practical pre-release gap. The comparison tool does not test credentials or access the reviewer’s environment.

Compare the previous and candidate releases

Keep a record of what you actually know. In the free browser tool, enter a verified previous-release snapshot and candidate-release snapshot. Run the comparison to inspect changed fields and export a report. Unknown information should stay unknown.

Use the release comparison tool

No account or real release required to try a sample. Your entered snapshots are processed in your browser.

Open free comparison tool →

What this guide cannot verify

We can check whether you marked reviewer instructions as provided, but we cannot verify private login success, Play Console settings or review outcomes.

Official documentation

Google Play — Prepare your app for review

Editorial note: Content checked against the linked official sources on October 28, 2026. This independent guide is informational, not legal advice or a guarantee of Google Play approval.