Skip to main content

Request & approval flow

Manual mode puts you in control of every install. You publish the app as a Public app so any organization can discover it—but instead of installing straight away, each organization must send you a request. The installation stays PENDING until you approve or reject it, so you decide exactly who gets access and with which scopes.

Example​

Let's follow one real request end to end.

The players

  • PixelInnovations — the owner. It publishes Star Industries as a Public app with Manual Approval.
  • Bitvero — the consumer. It requests to install the app, asking for the FILE scopes.

The flow at a glance​

Owner · PixelInnovationsMarketplaceConsumer · BitveroCreate app (Public + Manual)1Listed in the Marketplace2Request install & grant scopes3Request created — status PENDINGIf approvedApprove → status ACTIVE4If rejectedReject with reason → REJECTED5If cancelled firstCancel request → CANCELLED6After ACTIVE, either side can Uninstall or Revoke

Step by step​

1PixelInnovations creates the app (Manual Approval)

PixelInnovations creates Star Industries with Public visibility and Manual Approval, so every install needs its sign-off.

2The app appears in the Marketplace

The app is listed in the marketplace. Bitvero finds Star Industries under Public Apps and opens it.

3Bitvero requests to install it

Bitvero reviews the requested scopes—file.upload.write and file.details.read—and clicks Request Application. The request is now PENDING.

4PixelInnovations reviews and decides

In Received Requests, PixelInnovations sees Bitvero's pending request and the permissions it asked for, then Approves or Declines it.

What happens to the request​

A request always starts as PENDING. From there it reaches one of three outcomes:

ACTIVE

Owner approves

PixelInnovations approves the request. The installation goes live and Bitvero can start using the app.

REJECTED

Owner rejects

PixelInnovations declines the request, optionally with a reason. No access is granted.

CANCELLED

Consumer cancels

Before the owner decides, Bitvero can withdraw its own request.

Only the requester can cancel

Cancelling applies to the consumer's own pending request, and only before the owner approves or rejects. Once a decision is made, the consumer uninstalls (if active) rather than cancels.

After the app is active​

Once an approved installation is ACTIVE, either side can end it at any time.

Uninstall

Done by the consumer — Bitvero

Removes the app from their organization. The installation becomes UNINSTALLED and the app can no longer obtain tokens for that org.

Revoke

Done by the owner — PixelInnovations

Ends the installation from the app's side. The installation becomes REVOKED and Bitvero loses access.

Related