* I'd like to have a dropdown on the left side in which you can choose
the realm you want to manage, much like the "Current Profile" box in the
EAP admin console.
Instead of a dropdown, we have a list of elements you want to manage at
the left side.

I still want a dropdown like the "Current Profile" box in the EAP admin
console to pick which realm you want.
Why?

Because its simple easy one click? Rather than click, load a page, click
again? Simpler, less clicks, less realestate. Its an easy way of
navigating between the realms you have to manage while reducing the
amount of clutter on the page.

This would make sense if the applications presented at the sidebar where related to a specific realm. Something like: You are in [Realm 2]. Then Realm 2 could be a dropdown and the user could easily navigate to another realm. But in this context, he would see applications related to it, not manage the realm itself. To do so, the user could click in a link on the page to manage the specific realm that is related to the application being displayed.

In case of the application page, it would be nice to display somewhere
which realm the application belongs.

I thought we'd agreed that Application is not something created
separately from Realm? I think this would have an effect on your design
as there would be two less buttons at the top left corner. There would
be no "Applications" or "Realms" buttons.
Hadn't we agreed that, in case of the first application, Jared configure application AND realm options in the same page?
How will people see the list of applications and realms without "Applications" and "Realms" at the top bar?

Having Applications and Realms on the top bar makes it seem like they
are separate things that can be created separately from one another.
This just isn't true. Once you want to do Single Sign On (SSO) between
multiple applications, combining application and realm options on one
page just doesn't make sense at all. I thought I made that clear.

I may have misunderstood, but I thought it was possible to create a realm separately and then create an application and associate it with that realm.

I also understood that, in the moment of the application creation, the user could set new realm options (what creates a new realm) or choose to use information from a realm already created.

In case of multiple application associated to the same realm, we could display informations about the realm (not editable). This is useful for the user.

I proposed this in my last email of the thread "Admin UI", where I exposed many topics and looked for some clarification/agreement but got no response.

I still prefer the "Wizard" idea for first time users that was vetoed
down. I just don't understand Stian's dislike for this approach.
Wizards allow you to handhold users and explain each and every
configuration step. Now that we can do thick clients again via
Javascript there's really no good reason for disliking multi-form
configuration.

Wizard is good in some cases but I agree with Stian that it is not necessary for Keycloak now.

As it is, working witih applications is going to be a rare thing.
You'll create them once and almost never touch them again. Most work is
going to be around managing users (adding users and their mappings,
reseting credentials).

Ok, this can be done in the realm. But how the user access his applications? Are you proposing to not have a list of applications and a navigation for it, but only list applications inside the realms?

For social apps, there's a good chance they'll only interact with
keycloak only a few times when they are setting up their app and never
touch it again.

Ok. In this way we can make the realms more important (first in the navigation, at least).

Could you read my email "Admin UI"? After that, I propose a hangout to clarify some aspects. I'm kind off stuck without a common understanding.

Thanks,

Gabriel