Installable Applications
Installable applications let you publish an M2M application to the marketplace so other organizations can discover it, grant it scopes, and install it—turning a private backend integration into a product other teams can adopt.
Every installable application is an
M2M applicationat its core. It uses the same OAuth 2.0 Client Credentials model for backend access—installation simply controls which organizations may obtain tokens for your app and which scopes they were granted.
Roles & Actions
Two organizations interact with every installable app. Every action happens at the
organization level—any member with Developer Portal access acts on behalf of their organization; there is no separate "admin" role.
!
Owners Configure First
The owner organization must configure scopes and integrations before any consumer organization can install or use the app.
Owner Organization
The team that creates and configures the application.
- ✓Create & configure applications
- ✓Send invitations (partner apps)
- ✓Approve / reject requests
- ✓Revoke active installations
Consumer Organization
The team that installs and uses the application.
- ✓Install marketplace applications
- ✓Submit installation requests
- ✓Accept / reject invitations
- ✓Cancel requests / Uninstall apps
Three ways an app gets installed
An app's Visibility and Mode are set when it's created—see Create application → Visibility & Mode. Those two choices decide how, or whether, other organizations install it. Each path below is documented end to end.
A Private app is for use inside the owner organization only. It is never published and never enters the installation lifecycle—no installs, requests, invitations, approvals, or revocations. Everything below applies to Public and Partner apps.
Active instantly
The consumer installs from the marketplace and the app goes live immediately.
Read the flowOwner approves
Installing sends a request; the owner reviews and approves before it activates.
Read the flowInvite → accept
Invitations go to the selected business groups; invited orgs accept to install.
Read the flowInstallation lifecycle
Every install path—auto, request, and invitation—is tracked in a single installation record. The record does not fork into separate resources; the same record transitions between statuses.
Status reference
| Status | Meaning |
|---|---|
| ACTIVE | Installed and usable; the consumer org can obtain tokens. |
| PENDING | Awaiting owner approval (request) or invitee response (invite). |
| REJECTED | Owner rejected the request, or invitee declined the invitation. |
| CANCELLED | Consumer withdrew the request before the owner acted. |
| REVOKED | Owner ended an active installation. |
| UNINSTALLED | Consumer removed an active installation. |
Next steps
Auto install flow — Public + Auto
Request & approval flow
— Public + Manual
Invitation flow
— Partner apps
Create application — Visibility & Mode
M2M applications — the foundation installable apps build on