# Google Play Reviewer Access — Template

Copy this into the Play Console's **"App access"** section when submitting
for review, filled in with a dedicated demo account's real values.

**Never commit real credentials into this file or anywhere else in git.**
Everything below is a placeholder — fill in the actual values only inside
the Play Console form (or a password manager), never in a tracked file.

---

## Test account — Restaurant Owner

MenuKosh has three separate login surfaces. Reviewers evaluating the
Android app only need the **Owner** login — Super Admin is a
platform-internal role, not part of the restaurant-facing app experience,
and is intentionally omitted from this reviewer-access template.

- Login URL: `https://menukosh.pinakra.com/login` (Owner tab is selected by
  default)
- Username: `[REVIEWER_OWNER_USERNAME]`
- Password: `[REVIEWER_OWNER_PASSWORD]`

### What the reviewer can do with this account

- View the Owner dashboard, menu/category/item management, table
  management, staff list, QR code page, reports, and settings.
- Place a test order via the restaurant's own public QR menu (no login
  required for that half of the flow — open
  `https://menukosh.pinakra.com/menu/[REVIEWER_RESTAURANT_SLUG]` in a
  second tab) to see the order appear on the Owner dashboard.

## Test account — Staff

- Login URL: same as above, with the **Staff** tab selected
  (`https://menukosh.pinakra.com/login?role=staff`)
- Username: `[REVIEWER_STAFF_USERNAME]`
- Password: `[REVIEWER_STAFF_PASSWORD]`
- Shows the waiter/kitchen order-management view scoped to the same demo
  restaurant.

## Subscription state

- [ ] Confirm the demo restaurant's subscription is set far enough in the
      future that it will not expire mid-review (see the subscription
      banner tiers in the app — a reviewer landing on an expired-
      subscription screen mid-review will not be able to explore the
      dashboard).
- [ ] If review happens close to the demo subscription's end date, extend
      it manually before submitting rather than relying on the reviewer
      to renew it themselves.

## OTP / two-factor

- [ ] MenuKosh does not currently require OTP or two-factor authentication
      to log in (2FA was removed as a product decision) — no additional
      verification step should block the reviewer after entering the
      username/password above. If that changes in a future release,
      update this section with exact reviewer instructions for receiving
      the code.

## If the reviewer gets stuck

Provide this fallback contact in the Play Console form:

- Support email: `support@pinakra.com`
- Support phone: `+91 7275002472`

## Before submitting

- [ ] Log in with the exact credentials above yourself, right before
      submission, to confirm they still work.
- [ ] Confirm the demo account's role-based access matches what's
      described above (an Owner account that's accidentally Staff-scoped,
      or vice versa, will confuse the reviewer).
- [ ] Remove or rotate these credentials after the review period if the
      demo account isn't meant to stay active long-term.