Overview

As a critical communication tool in user registration and login journeys, emails offer opportunities to provide important alerts and updates in a personalized manner. The ability to customize email content not only enhances the user experience but also adds a unique touch to your brand communication. This document focuses on various features that allow the customization of transactional emails within the Next Identity platform.

Features for Customization

Transactional email content can be personalized across these categories:

1. Primary Translated Email Text: This is the standardized text in your emails, customizable for your organization and translatable into the numerous languages supported by Next Identity.

2. Core User Data: Enhance personalization by incorporating key user attributes from the local IDP database:

   • End user's first name
   • End user's last name
   • End user's email address

3. Application Specific Variables: Adapt to the needs of each integrated application with these customizable elements, such as the application name and brand factory assets.

4. Next Identity User Metadata: Include non-translatable and non-PII user details stored in the Next Identity service in selected email templates.

5. Magic Links and Pins: These tools, vital for transaction completion, offer customization options detailed in a separate feature document.

Customization Workflow

The Next Identity service employs the customer's email service provider to dispatch these transactional emails. Here's how customization is facilitated:

• Email Text: Sourced from the local IDP translation/email service at the email trigger point. Customers can modify the base text according to their preferences.

• User Data & App Variables: Extracted from the local IDP database and client settings, respectively, at the email trigger time and integrated into the email text.

• Next Identity User Metadata: Pulled from the Next Identity database at the email trigger, parsed, and subsequently included in the IDP-generated email text. It cannot be translated and will appear exactly as is in the Next Identity database.

Product Enablement

Customer Requirements

Next Identity maintains a set of customizable and translated email templates for each enterprise customer. During the onboarding process, the base email text is jointly discussed and refined, then translated into the supported languages.

To use dynamic Next Identity metadata in user emails, customers must:

• Use the Next Identity token delegation service.
• Utilize the latest version of the Next Identity Hosted Journeys or API integration.
• Implement the Next Identity Consumer Access Control feature for tracking user-to-application associations.

Customers are responsible for providing updated text to the Next Identity service team as desired.

For a list of supported languages, please visit here.