Invitation flow
Partner mode lets you offer your app to specific organizations only. Instead of listing it in the public marketplace, you publish it as a Partner app and choose exactly which business groups may see it. Organizations in those groups can install it in two ways — by receiving an invitation you send, or by finding the app directly in their Partner Apps marketplace tab — no invitation required.
Example
Let's follow one real invitation end to end.
The players
- Stylenest Corporation — the owner. It publishes a Partner app called Nexora Labs, invites specific organizations, and picks the scopes each invitation grants.
- bluelatte — an invited organization. It receives the invitation, reviews it, and decides whether to accept.
The flow at a glance
Two ways partners can reach your app
Once you create a Partner app with business groups selected, organizations in those groups can install it through either path — you don't have to use both. Click a path to see its step-by-step flow.
Send an invitation (active push)
From your app's Installations page, open Send Invitation, pick the organizations you want to onboard, and choose their scopes. The platform emails each org a personal invite link — they Accept or Decline.
Best for: proactively onboarding key partners
Let them discover it (no invitation)
Skip the invitation. Organizations that belong to the business groups you selected when creating the app automatically see it under Partner Apps in their marketplace and can click Install directly.
Best for: letting eligible partners self-serve at their own pace
Step by step Path A
What happens to the invitation
An invitation always starts as PENDING. From there it reaches one of three outcomes:
ACTIVE
Org accepts
bluelatte accepts the invitation (or installs it directly). Nexora Labs goes live for bluelatte.
REJECTED
Org declines
bluelatte declines the invitation. No access is granted, and Stylenest Corporation is notified.
CANCELLED
Owner withdraws
Before bluelatte responds, Stylenest Corporation can withdraw the invitation.
Each invited organization's status is tracked independently. One org accepting, declining, or installing manually has no effect on the others.
After the app is active
Once an accepted installation is ACTIVE, either side can end it at any time.
Uninstall
Done by the invited org — bluelatte
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 — Stylenest Corporation
Ends the installation from the app's side. The installation becomes REVOKED and bluelatte loses access.
Related
Auto install flow — Public + Auto, no approval step
Request & approval flow — Public + Manual, when you vet each install
Installation lifecycle — every status and transition
- Create application — Visibility & Mode