OAuth Clients, Now Managed From the Admin Panel
Instance operators can now register and manage OAuth clients directly from the admin settings, without hand-editing config or shelling into a server.
For a long time, wiring up a new OAuth integration on a self-hosted instance meant one of two things: editing a config file and restarting the process, or writing a one-off script against the database. Neither is a great story when you're trying to hand the keys to an ops team, and neither leaves an audit trail worth reading.
So we moved OAuth client management into the admin panel itself. Admins can now register and manage instance-wide OAuth clients from a dedicated settings page.Manage OAuth Clients (Admin)
Why this lives in the admin panel
OAuth clients are an instance-level concern. A client credential grants an external application the ability to act against your instance's API surface — that's not something an individual user should be minting, and it's not something that should require a deploy.
Putting it behind the admin panel gives us the right permission boundary for free: whoever can administer the instance can issue credentials, and no one else can. It also means the operation looks like every other admin action — same navigation, same auth, same session. There's no separate tool to learn and no separate secret to protect.
What it unlocks
The immediate win is speed. Registering a new client is now a form, not a deploy, which means integrations that used to take a ticket and a maintenance window can be set up in the time it takes to name them. A few concrete things this makes easier:
- Standing up a staging OAuth client for a partner without touching production config.
- Rotating credentials on a schedule instead of a panic.
- Cleaning up clients that were spun up for a proof-of-concept and forgotten.
The second-order win is visibility. Because clients are now first-class objects in the admin UI, there's a single place to see what's registered against your instance. That's the kind of thing you don't realize you were missing until the first time an auditor asks.
What's next
This is the foundation, not the finish line. With clients as managed objects, the natural next steps are richer scopes, per-client rate limits, and an activity view so admins can see which integrations are actually being used. If you're running a self-hosted instance, the new page is live in admin settings — the paired help-center article walks through the registration flow step by step.