Cloud Identity Engine: one login for every group

A merger brings a second identity provider, an acquisition a third, contractors a fourth, and admins had only two bad options: a separate login portal per group, or one method forced on everyone.

Before drawing a screen I mapped the flow end to end: open the profiles list, name a profile, then choose whether it authenticates one way or several. That single question is where the path forks. One method is a short run to the finish. Several picks up a priority order, a required default, and the group mapping that resolves against them.

Laid out that way, a wizard was clearly the wrong shape. It would have put each of those decisions on its own step, and they are only meaningful next to each other. A priority order means nothing until you can see the groups it resolves, and a default means nothing until you can see what it is catching. Admins configuring something this consequential need to see the whole setup at once, so I kept it on one page and let complexity reveal itself only when it's needed.

Groups that still need a method sit on the left, assigned ones on the right, so coverage reads at a glance. The fallback and priority order are treated as required security decisions, not optional fields.