Journey types

When creating a new journey in Mosaic Orchestration, there are several journey types to choose from, each suited for different use cases. Understanding these types will help you select the most appropriate option for your workflow:

• Client SDK Journey : This journey type is intended for workflows that require client-side interactions, such as collecting user input, performing device operations, or presenting authentication methods. It is operated within your client application, where the user interaction happens. To do so, it leverages the Mosaic SDK (available for web , iOS , and Android ) to handle client-side interactions before sending data back to the server for further processing.
• SSO Journey : A specialized journey type designed for running orchestrated Single Sign-On (SSO) scenarios tailored to your business needs. It manages SSO sessions and allows users to authenticate once and access multiple applications or services without needing to re-enter their credentials. For a hands-on example, see our SSO journey tutorial .
• Backend API (single call) : This type of journey is strictly for backend-only operations and does not allow client-side steps. It is invoked as a single call from a backend service, typically used for service-to-service interactions or automated processes. This journey type is suited for workflows that may include multiple backend steps, such as updating a user record or calling external services, as long as they don’t require any client interaction. For more, see our Backend API journeys overview.
• Sub-Journey : A sub-journey is a reusable component that you can integrate into other journeys. This allows you to create standardized workflows and reuse them across multiple journeys, simplifying the management of complex identity processes.