Skip to content

Approving an app install request

An app can ask, from its own side, to be installed on your store. The link it gives you opens the Install an app screen at /apps/authorize, with the request named in the address. The screen’s description is: “An app is asking for access to this store. Read what it may do, then approve or decline.”

It needs the settings.manage permission, the same permission as the rest of the Apps settings. If you open the link without being signed in, you are taken to the sign-in page and brought back to the same address afterwards. The link by itself authorizes nothing: it names a request, and only a signed-in staff member of the same store can answer it.

  • App — the app asking.
  • Made by — its maker.
  • After you answer, you go to — the address the browser goes to next. An app can call itself anything, but this address has to be one the app registered, so it is the line the app does not control.
  • Status — Waiting for your answer, Approved, Declined or Expired.
  • What it may do — each permission written as a sentence with its identifier beside it. Some permissions carry a label saying they are not active on this platform.

If the app is already installed the screen says “Approving adds the permissions below to the ones it already has.”

Two buttons: Approve and install and Decline. The answer carries only yes or no; the permissions and redirect address were stored when the app asked, so changing the page cannot change what is approved. After answering, the screen says “Taking you back to the app…”.

If the link does not name a pending request in this store, the screen is titled No install request here and says: “This link does not name a pending install request in this store. It may have expired, or belong to another store: switch to that store and open the link again.” If the request was already answered or has expired, the message is: “Start the install from the app again.”