> ## Documentation Index > Fetch the complete documentation index at: https://docs.ulm.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # About Notification Service Templates Digital Identity Management provides templates that support branding and customization. Each template contains dynamic notification variables that are configurable, enabling the template to be tailored with your organization's information and branding. All templates are stored by Digital Identity Management and organizations are responsible for their own template configuration and can download, edit, and upload the templates from the [Admin console](branding). Several Digital Identity Management templates are embedded with predefined Thymeleaf variables. For more information on the Thymeleaf template engine, see the [Thymeleaft tutorial](https://www.thymeleaf.org/doc/tutorials/2.1/usingthymeleaf.html). The use cases available for users are: * Signup with email and password * Signup with mobile and password * Signup with social media account (Apple, Google, Facebook, LinkedIn, Microsoft) * Forgot/reset password * Profile management: * Update display name * Update preferred language * Add/update/remove email * Add/update/remove mobile * Update preferred contact method * Update password * Add/remove social login See [Notification Service Email Templates](notificationEmailTemplateDetails_r) and [Notification Service SMS Templates](notificationSmsTemplateDetails_r) for the available use cases, supported templates and variables. ## Template Types: Email and SMS There are two types of templates based on the recipient's contact channel type: an SMS template for sending notifications to a user's mobile number, and two interrelated email templates for sending notifications to a user's email address (one template for the email header, and one for the email body). ## Template Fields Every Process supports a collection of template fields that can be added to that Process' corresponding template(s). When a user completes a Process (such as when a user successfully completes an desired action), Digital Identity Management pulls the relevant information for each template field (e.g., user name, email address, etc) and populates the notification message with that information. As an example, the first line of a template uses a field in the salutation like "Hi \[firstName], thanks for signing up with ABC Inc" then the actual notification would read "Hi Jane, thanks for signing up with ABC Inc." ## Notification Variables Digital Identity Management supports the use of notification variables in all template types that allow you to further customize your message to users. The dynamic notification variables are substituted by the Digital Identity Management process when the message is being generated. ## Email Template Structure The email header and message files are written using CSS, HTML, and ThymeLeaf. See [Manage Email Templates](templatesEmail) for more details on how to create your notification message templates. **Example:** **Verification of authentication identifier during onboarding:** This use case requires two email template files. 1\) Email Header: verification-of-authentication-identifier-during-onboarding\_header.txt 2\) Email Message (body): verification-of-authentication-identifier-during-onboarding\_body.html **Email Header** The three common header fields used in the header file (.txt) are **To**, **From** and **Subject**. The supported fields are replaced with values that have been entered/dynamically set by the Digital Identity Management Process when sending a message. The following code block is from the .txt header file: ``` To: <[(${message.emailAddress})]> From: [(${message.from})] Subject: Finish operation token PLEASE ``` The message (body) file can be used to customize a message that is used in emails sent within your organization.The file is written in html. The template supports the following variables: * displayName * actionTokenURL * customToken The customToken represents the OTP verification code that the user enters on their UI to verify their email. Alternatively, the user can click the link, which is the actionTokenURL, to verify their email address. Digital Identity Management Email Message Template html file **Email Message (Raw mode)** See the example email message below for more details regarding elements that can be updated/modified: ``` Welcome to Amdocs
Email has been successfully sent through dispatcher: ${dispatcherName}
``` ## SMS Template Structure A SMS template file only contains the one header (txt) file and is written is text. See [Manage SMS Templates](templatesSms) for more details on how to create your notification message templates. \*\*Example:\*\***Verification of authentication identifier during onboarding:** The use case requires one SMS template file: * verification-of-authentication-identifier-during-onboarding\_header.txt **SMS Header** The templates support the following variables: dispatcherName and customToken. The dispatcherName is a dynamic variable that is replaced with your SMS dispatcher name such as Twilio. The customToken is replaced with a generated token and updated in the message. The text in the header file (.txt) can be changed/updated with your organization's own message. The supported fields are replaced with values are entered/dynamically set by the Digital Identity Management process when sending a message. The notification variables are replaced with values that you've configured in your template files. The following code block is from the SMS header (.txt) file: `Thank you for using Digital Identity Management. This is a short message confirming that you have successfully sent it through dispatcher: [[${dispatcherName}]]Use the following code: [[${customToken}]] to complete this operation.` * **[Manage Email Templates](../topics/templatesEmail)** * **[Manage SMS Templates](../topics/templatesSms)** **Parent topic:**[Branding](../topics/branding) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.