Propagate Changes

The Propagate Changes feature in Next Identity allows you to efficiently replicate configuration updates across environments — such as Development, UAT (Stage), and Production — ensuring consistency and reducing the risk of manual errors. This structured workflow is essential for managing configuration at scale, promoting safe deployment practices, and maintaining reliable system behavior across your environments.

Before you can propagate changes, make sure that the client has already been created in all target environments (e.g., Production).

In Next Identity, clients are organized into properties, which represent logical groupings aligned to your business. Each property and its clients typically exist across multiple environments, such as:

• Development (lowest environment)

• Stage/UAT

• Production

This architecture enables you to:

• Make updates in a controlled environment (e.g., Development)

• Test changes safely

• Propagate updates to upper environments once validated

For example, a customer with three properties — each replicated across three environments — can test features in Development and promote them to Production in a streamlined and consistent manner.

Changes Implemented in Lower Environment (Development) that Need to be Propagated

You can only make changes in the lowest environment of your pipeline (usually Development). Once these changes are saved, you can propagate them to upper environments using a guided process. This helps avoid discrepancies and ensures changes are properly reviewed before reaching production.

Let’s say you want to enable Two-Factor Authentication (2FA):

1. Enable 2FA in the Authentication Journey for your Development environment.

2. Test the login flow using the Run feature.

3. Once verified, start the propagation to Stage and then to Production.

1. After saving changes in Development, a red dot appears next to the next environment tab (e.g., Stage), signaling a difference between environments.

2. Select the highlighted tab. A message will appear explaining:

   • The detected inconsistencies

   • The next available action: Start propagation

3. Select Start propagation to open a summary of changes. You’ll see:

   • Each updated item

   • Its current value in the target environment

   • The updated value from the source environment

4. Review the items carefully. If everything looks correct, select Start propagation again.

5. A confirmation modal appears. Optionally add a comment to document the change for audit purposes.

6. Select Propagate to apply the changes to the selected environment.

7. If this is not the final environment, the process can be repeated. A red dot will now appear on the next environment in the pipeline.

Once propagation is complete:

• The red dot disappears from the updated environment.

• Configuration is now aligned with the source environment.

• The process can continue sequentially until all environments are updated.

Tip: Use comments during propagation to create a clear, auditable history of changes across environments.

• Always test your changes using the Run feature before propagation.

• Use propagation to maintain consistency and prevent manual misconfigurations.

• Coordinate with your team if multiple users are making concurrent updates across properties.

• Journeys Builder Overview

• Customize Login

• Customize Registration

• Customize Profile Update

• Set the default language and supported languages

• Manage translations

• Manage Email Messages

• Manage SMS Messages