App access for review
Reviewers need a reliable path through the app, not a vague login note.
If your Android app needs login, OTP, subscription, location, admin approval, demo data, or a staged account state, Play Console app access instructions should make review simple and repeatable.
App access instructions are easy to underestimate. A founder may write "use test login" and move on. But if the reviewer cannot reach the feature, cannot receive an OTP, lands in an empty account, or needs a geography-specific password, review can stall.
This guide explains how to prepare reviewer access instructions before submission.
Official source note: Google's guidance for sign-in details says clear and simple instructions help the review process, and location-dependent passwords should be replaced with sign-in details that are valid regardless of user location. See Google's current instructions: Requirements for providing sign in details for review.
Reviewer access standard
Quick answer
App access notes should let a reviewer reach the important app flows without support.
Prepare:
- Dedicated reviewer test accounts.
- Passwords or access methods that work from any reviewer location.
- OTP, 2FA, magic link, or phone verification strategy.
- Demo data that shows meaningful screens.
- Subscription, payment, admin, or invite-only access instructions.
- Step-by-step path to restricted features.
- Notes for permissions, location, Bluetooth, camera, or device setup if needed.
- Rotation plan after review.
When app access instructions are needed
Provide app access instructions when the reviewer cannot evaluate the app from a fresh install without extra context.
| App behavior | Reviewer access need |
|---|---|
| Login required | Test username, password, and recovery-free access path. |
| OTP required | Stable test code, test phone flow, or alternate review-safe access. |
| Subscription required | Test entitlement or explanation of how to reach paid screens. |
| Admin approval required | Pre-approved demo account or bypass for review. |
| Location gated | Location-independent test access or clear demo path. |
| Empty account state | Seeded demo data showing real app value. |
Reviewer access checklist
Review access preparation
- Create test accounts separate from real users.
- Use dummy data, not customer data.
- Confirm credentials work after a fresh install.
- Disable or document temporary onboarding blocks.
- Provide steps from install to the feature under review.
- Include sample data for dashboards, orders, chats, bookings, or reports.
- Confirm support email can respond to review questions.
- Remove or rotate temporary credentials after review if needed.
Test account patterns
Use one stable reviewer account
Best for apps where a single login shows the core product clearly and no special role is required.
Provide role-specific accounts
If the app has customer, admin, delivery, clinic, seller, or staff roles, give reviewers a clean path for each required role.
Avoid review being blocked by phone OTP
Use a test OTP strategy approved by the product team so reviewers are not dependent on a real phone number controlled by staff.
Expose paid screens safely
Use test entitlement, sandbox purchase paths, or demo access so reviewers can see subscription-gated functionality.
Common review blockers
Empty demo account
The reviewer logs in but sees no data. Seed the account with realistic dummy records.
OTP sent to founder phone
Reviewers cannot use a phone number that requires a founder to forward codes manually.
Geo-gated credentials
If the login only works in one city, store, or clinic, provide a location-independent route for review.
Unclear paid flow
If major functionality is behind a subscription, explain how reviewers can reach it without a real payment problem.
Safe credential handover
Keep reviewer credentials in the Play Console app access section and internal runbook. Do not publish them in public docs or screenshots. Use dummy emails, demo data, and credentials that can be rotated after review.
FAQ
Do I need app access instructions if my app has no login?
Maybe not. But if any feature requires credentials, payment, invite, geography, admin approval, or special setup, provide instructions.
Can I send reviewer credentials by email later?
Put the required instructions where Play Console asks for them. Do not rely on a separate email being seen in time.
Should the test account use production or staging?
The reviewer should evaluate the submitted production-intended app. If staging data is used, make sure the app behavior and policy declarations still match.
Can Shinka prepare app access instructions?
Yes. We can map the app's gated flows, create dummy test data, define credentials, and write clear reviewer notes.
