Review apps
Go through requests to widen an app's visibility or promote a version to production, and approve or reject them.
This page covers App services › App review in the admin console.
It's about looking at what developers submitted and either approving it or rejecting it with a reason.
The submitting side is covered in Visibility & access and Deploying to staging.
There are two kinds of review
Both are called "review", but you're checking different things. Opening the detail pane makes it obvious which one you're looking at.
| What was requested | What appears on screen | |
|---|---|---|
| Visibility review | Open the app up to more people | A Requested scope field |
| Promote review | Ship the version verified in staging to production | A What goes to production section |
Getting around the review screen
The list is on the left, the detail on the right. The list has two tabs.
- Pending — requests you haven't handled. The count shows on the tab, and the same number appears on App review in the left menu
- History — requests already handled: approved, rejected, cancelled, and revoked
Pick one on the left and its detail opens on the right.
What you look at to decide
The detail pane is split into sections.
Developer info — who submitted, and when: name, email, submission date.
App info — most of the decision lives here.
| Field | What to check |
|---|---|
| Domain | Clicking it opens the actual app in a new tab. Open it and see for yourself |
| Category | Whether it's classified correctly |
| Requested scope | How far they want it opened (visibility reviews only) |
| Reason | Why they need it |
| Description | The description that will actually appear in the store |
What goes to production — promote reviews only. Cards show which version production moves from and to, and which commits, along with the pre-deploy check results. The security scanner verdict and agent check line are here too.
Approving
Approve opens a confirmation dialog.
For a visibility review, you choose the final scope in this dialog. It defaults to what the requester asked for, and you can change it — narrower or wider. The moment you approve, the app opens at that scope.
Think twice about External. Approving at External means anyone on the internet can reach the app without signing in, and search engines may index it. The dialog warns you again.
Rejecting
Reject opens a dialog asking for a reason. The reason is required — the reject button stays disabled while it's empty.
What you write goes straight to the requester. Be specific about what to fix before resubmitting.
The description is identical to the one-line summary. Please add what problem it solves, its main features, and how to use it, then resubmit.
Rejected requests move to the History tab, where the reason is kept alongside who handled it and when.