An admin UI that's safe to put in your customer's hands.
Customer admins shouldn't see your Keycloak console. The Admin Portal is a scoped, embeddable UI that lets them manage their own users, roles, and SSO — and nothing more.
Exposing the Keycloak console to customers is a non-starter.
Too much surface area
The Keycloak admin console shows realm-wide settings. One misclick and a customer changes your global config.
Wrong language for customers
Realms, clients, identity providers — Keycloak's terminology doesn't match what your customer thinks about.
Brand mismatch
Keycloak's default UI looks like Keycloak. Your customers expect your brand inside their settings.
A portal scoped to the customer, not the realm
Per-Organization scope
Every action is scoped to one organization. No cross-tenant leakage by construction.
Customer-shaped vocabulary
'Members', 'Teams', 'SSO' — not 'Users', 'Roles', 'Identity providers'.
Embeddable in your app
Drop the portal into your existing admin UI, theme it, and it inherits your brand.
Reuses Organizations + IdP Wizard
Built on the rest of the suite — every org capability surfaces in the portal automatically.
Where the Admin Portal goes
Anywhere customer admins need to manage their own identity surface without bothering your support team.
Customer-safe identity management
Member management
Invite, remove, suspend, change role — all via the portal.
SSO setup (with IdP Wizard)
Customers configure their own IdP. No tickets.
Role assignment
Per-Org roles, no cross-tenant leakage.
Audit log view
Customer admins see what happened in their org.
Brandable
Logo, colors, copy. Fits inside your app.
iFrame or React SDK
Embed the portal with one tag or one component.