Publish an app to the marketplace
As a developer, you register a third-party app, define the scopes it requests, create the OAuth credentials (client_id and client_secret) and submit the app for review. Once the team approves and publishes it, any tenant can install your app.
The developer portal is under Apps, on the Developer tab. There you register an app, define what it can access, generate the OAuth credentials and submit it for publication. Only administrators can manage apps.
Register and configure the app
- Open Apps and go to the Developer tab. Click New app.
- Fill in name, identifier (slug), short and full description. The icon and website URLs, when provided, must be https.
- Check the requested scopes: ask only for the minimum needed. The tenant grants a subset on install.
- If the app embeds widgets, list the allowed origins (one per line, always https). Add webhooks if the app receives events.
- Save the draft. You can edit while the app is a draft or was rejected.
OAuth credentials
Under OAuth credentials, create a client for the app. Choose the client scopes (always a subset of the app scopes) and enter the redirect URIs, which are checked by exact match during consent. On creation, the client_id and client_secret appear only once.
Submit for review and publish
- With the app ready, click Submit for review. The status changes to Under review.
- The team reviews and approves or rejects with a note. If rejected, adjust the app and submit again.
- Once approved and published, the app appears in the catalog and any tenant can install it.
For the OAuth flow details (authorize, token, refresh and PKCE), see the developer documentation. The app's access is always limited to what the user consents to on install.