The job of this console
Register an app, understand usage, then issue keys or subscribe webhooks without scattering credentials in chat. Revoke from the same hub when an integration leaves.
Admin · Extensibility
Developer Portal
Register apps, review usage, then manage API keys and webhooks from the same hub.
Scroll to Flowcharts. Scenario: Register an integration app.
Extensibility hub
Apps, keys, and webhooks from one door
The developer portal is where you register apps, review usage, then manage API keys and webhooks. It is the hub; the key and webhook registers are the sharp tools.
Admin → Developer portal
Route
/admin/developer
Org flag developerPortalOverviewEnabled
HR Admin · Org Admin · integration owner
Seat at the table
Administrators and named integration owners. Ordinary employees do not open the portal. External vendors receive credentials once, not a login to this console.
The working rhythm
Open the hub, add or select an app, jump to API keys or webhooks, complete the issue or subscription, store the secret offline. Review usage when a partner says they are throttled.
Moments that bring you here
First connector. A vendor rotation of secrets. After a leaked key. When webhook delivery failures pile up.
ⓘ
Secrets are shown once
The portal stores metadata, not a recoverable plaintext vault. If a secret is lost, revoke and issue again.
Flowcharts
1 — Register an app
Create the app record, then issue keys and optional webhooks.
flowchart TD
A[Open Developer portal] --> B[Register app]
B --> C[Issue API key]
C --> D[Optional webhook]
D --> E[Monitor usage]
- 1Open portalAdmin → Developer portal.
- 2Register appName, owner, and scopes.
- 3Keys & webhooksHub tabs for day-two operations.
- 4Watch usageRevoke unused keys.
Overview
Extensibility is gated by developer flags. Tokens must not be pasted into docs or AI logs.
How to use
1. Least privilege scopes
Do not issue blanket admin keys.
2. Rotate regularly
Revoke on owner change.
3. Hub tabs
API keys and Webhooks are sibling consoles.