Onboarding is where a platform either earns its integration story or admits it does not have one. This company drove value through a combination of platforms and data, but the customer experienced that combination as five separate logins.
The migration constraint
Migrating a large user base to new authentication is one of the few product problems where a technically perfect solution can still fail completely. If the transition is confusing, users do not file a bug — they call support, or they stop logging in. The design constraint was therefore continuity: every existing user had to land somewhere they recognised.
Entitlements are a product problem
The five applications each had their own model of who could do what. The instinct is to unify them at the data layer, which is a multi-year program. The faster path was to unify them at the experience layer first — one enablement flow that understood all five models and presented a single coherent picture — and let the underlying consolidation follow.
Self-service as deflection
The single highest-leverage decision was giving client champions the ability to manage their own authorized users. It removed an entire category of support ticket and, more importantly, removed the delay between a customer needing access and getting it.