Journeys Builder Overview
What It Is
The Journeys Builder is a visual, no-code interface in Next Identity that enables you to design and manage user identity workflows—such as login, registration, and profile updates—without relying on engineering support.
It centralizes the configuration of user journeys at the client level, making it easier to control how users interact with your application across all environments.
Why It Matters
Managing identity flows can be complex and time-consuming. The Journeys Builder helps streamline this process by providing:
A visual flowchart that shows how each journey is currently structured
Component-level configuration of steps, screens, conditions, and actions
A built-in preview and settings panel for additional customization
A review and propagation workflow to manage environment-specific updates
How It Works
Accessing the Builder
Each supported journey is represented as a card within the Client Details screen. Available journey types include:
Login
Registration
Password Recovery (coming soon)
Profile Update
To make changes:
Locate the card for the desired journey.
Select the edit button (pencil icon) on the card to enter the builder.
You’ll be taken to a flowchart view that represents the current journey configuration.
Each element in the flow (step, condition, screen, or action) may include additional settings. Use the settings button (gear icon) next to these elements to open their configuration panel and preview changes.
Note: Only users with the appropriate permissions will see the User Journeys section. Some users may have view-only access, while others may have full editing capabilities, depending on their assigned roles.
Making and Saving Changes
Changes can only be made in the lowest environment (e.g., Development).
In upper environments (e.g., Production), changes must be applied through the propagation process to maintain consistency and deployment control.
Once you edit a journey:
A Review Changes section appears at the bottom of the screen.
You can review and save your updates in the current (lowest) environment.
After saving, you’ll be redirected to the Client Details screen.
Propagating to Other Environments
After saving changes in the lowest environment (e.g., Development), a red dot appears next to the next pipeline environment tab (e.g., Production) to indicate pending changes.
To propagate:
Select the target environment tab.
Use the Start propagation action.
Review the proposed changes.
Select Start propagation again.
A confirmation modal appears where you can optionally add a comment for auditing.
Confirm by selecting Propagate.
Note: Repeat this propagation process for each remaining environment until changes reach the highest one in your pipeline.
Testing Changes with the Run Feature
After saving updates to any journey, you can test it directly from the Client Details screen.
Each journey card includes a run button (play icon). To test the flow:
Select the run button for the journey you want to simulate (e.g., Authentication).
This opens a live preview that reflects the most recent changes in the current environment.
Use Cases
Empower non-technical users to manage identity workflows
Ensure consistency and security across environments
Safely test and validate configuration updates before promotion
Best Practices
Always test your journey using the Run feature before propagating
Use descriptive comments during propagation for audit clarity
Collaborate with developers when your flows require external integrations