Driven by entitlements
The portal renders from the same entitlement data governance works on, so it cannot drift from what access the user really holds.
Every entitled application, in one place
A personalised portal listing exactly the applications a user is entitled to — and nothing they are not.
Users should not need to remember which systems exist, where they live, or which of them they are allowed to open. The launchpad shows each person the applications their entitlements actually grant, drawn from the same identity fabric that governs access, so the list is accurate the moment entitlements change.
How App Launchpad works
The mechanics behind the capability — what the platform does, and where it does it.
One-click launch
Opening an application from the launchpad carries the existing session, so there is no second authentication.
Self-service alongside
Access requests, profile, security settings and request history sit in the same portal, so users are not sent elsewhere.
Nothing they cannot reach
Applications a user is not entitled to are simply absent, which avoids both confusion and speculative requests.
What it changes
Who feels the difference once App Launchpad is in place, and how.
End users
People find their tools
New joiners in particular stop asking where things are, because everything they are entitled to is on one screen.
Service desk
Fewer "how do I get to" tickets
Discovery questions largely disappear when the answer is always the same page.
Security
Shadow access becomes visible
When the portal is the way in, use of unmanaged routes stands out rather than blending in.
Governance
Entitlements made tangible
Managers reviewing access can see what a person actually has, which makes certification decisions better informed.
See App Launchpad in context
It works because the other capabilities share the same identity fabric. The quickest way to judge that is to watch it run against your own use cases.