Put an ESI journey inside the experience you already have.
Embed career, employee, programme or decision journeys without rebuilding the underlying logic.
The problem
Partners ask for a copy of ESI. A copy drifts, and private user context leaks through a broad key.
The decision
Which modules, whose brand, and which user-level permission is required before any context moves?
How it works
- Tenant settings would hold name, modules, and organisation content.
- Journeys stay the same objects an employee or a citizen already uses.
- An API would be scoped, revocable, and versioned. A key does not open My ESI.
- User-context calls need that user’s permission.
What the organisation sees
Its own tenant configuration and organisation content.
What stays private
Another tenant’s data, and a person’s My ESI unless a field-level share exists.
The pilot embeds the relocation journey with a short-lived signed token. A key does not open My ESI. DNS for a custom domain is not claimed as live.
Explore. Select. Innovate.