> ## 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 Services Digital Identity Management generates and delivers notification messages to guide users through a series of interactions or steps in a process on their user journey (such as onboarding with social account). Process steps or interactions are supported by Digital Identity Management's [REST API-based Processes](../../processGuide/topics/c_processOverview). Your organization integrates these processes into your web application(s), that users invoke through standard processes in the user lifecycle (e.g., onboarding, password management, service sharing). ## What are Notifications Notifications messages are sent to users with a Digital Identity Management [action token](../../processGuide/topics/c_actionTokens) that may require the user to complete a desired task and invoke a subsequent Process. You can integrate your own notification templates and provider(s) to send notification messages to the users that can be informational, or a request to the recipient to complete an action. The following are some examples of Notification Services when Digital Identity Management generates and delivers a notification to the user on the user's contact channel, also know as the Preferred Notification Channel (PNC): * An anonymous user is required to verify ownership of an email address during their [onboarding](useCaseAuthV2EmailMobileOtpLinkPwLess) process. Digital Identity Management sends an email notification to the user with a one-time password (OTP), delivered by the service provider configured. * An anonymous user selects a "Forgot Password?" option and completes the [Recover ID Process](../../processGuide/topics/c_forgotPassword). Digital Identity Management sends a notification, with an action token for the password reset, to the specified contact channel. * An authenticated [user removes](../../processGuide/topics/c_removeUserAttribute) one of their registered authN IDs from their profile. Digital Identity Management sends a notification to the user's preferred contact channel to confirm that the authN ID was removed. ## How Notification Services Work Digital Identity Management references notification templates to construct and deliver notifications using the Digital Identity Management services configured within your tenant. The Digital Identity Management Notification Services use the following components to generate, dispatch/deliver notification messages: * [Notification Templates](templatesAbout): Digital Identity Management stores Notification templates that are made up of text, HTML (email body file), and template fields. Each Digital Identity Management Process uses a set of templates to complete different task(s), The supplied email/SMS templates can be downloaded/modified with your organization's message type/structure (i.e., token types) based on HTML & thymeleaf templates stored in Digital Identity Management service within your tenant. When a user completes a Process step (e.g., verify ownership of an email address), the Process generates a notification by referencing the associated template(s), constructs the notification message, and delivers it. Two types of templates are available based on the user's contact channel type: * SMS template(s) for sending notifications to a user's mobile number. * Email (SMTP) template(s) are constructed from two template files (header/body) for sending notifications to a user's email address. * [Service Providers](provider): The configured service provider(s) dispatches and delivers notification messages to the user on the specified notification channel (email/SMS). Digital Identity Management supports the integration of external provider(s) using your organization's settings, in addition to the built-in provider services available in non-production environments for each channel type. ## Manage Notification Services Notification Services are managed from the **Admin console** > **Branding**where you can manage service providers, templates and customize your themes/branding to be used in your notification messages. **Use the Digital Identity Management Notification Service** With out-of-the-box default settings, most Digital Identity Management Processes send **both** a long-form clickable link **and** a short-form custom OTP to the selected contact channel. Digital Identity Management controls what token types are sent on each channel type based on HTML & thymeleaf templates stored in the Digital Identity Management data store. The notification templates controls the message content (messaging, branding) as well as the token type (link, OTP, or both) based on the user's channel type (email or mobile). These templates are set according to your business requirements during the initial onboarding and integration phase between your business and Digital Identity Management. For example, as a best practice, you can opt to send only clickable links through email notifications and only OTPs through SMS. Notification settings can be established for your organization as a part of the onboarding and discovery sessions between you and [Digital Identity Management Support](m1ConnectSupport) Services. **Use your Notification Service (external)** Digital Identity Management supports the MarketONE CSP Adapter API to provide large-scale Service Providers a method to leverage their existing notification system. When a user completes a Process, Digital Identity Management sends all of the relevant content (user information, redirect+token URL, custom token OTP) to your own notification delivery system via this API. Your notification system generates and sends the required notifications to the user's contact channel. Whether using Digital Identity Management's notification or your own external notification system, confirm what types of action tokens will be sent to the users, and build your client application UI pages accordingly. For example, if you're only sending clickable links (long token URLs) to your users, then you don't require any kind of OTP (short token) verification. Alternatively, if you're only sending OTPs on one channel, but both a clickable link and OTP over a different channel, then you'll need to support each channel-driven flow on the client application UI(s) Digital Identity Management's built-in provider(s) are used for testing notification services in non-production environments such as **PDT**. To integrate your production environments, merchants integrate a custom external email/sms provider to process messages. * [Configure an Email Provider](providerEmail) * [Configure a SMS Provider](providerSms) **Use Digital Identity Management Templates** Digital Identity Management supplies default templates to download/upload and stores the templates that are dispatched/delivered with your configured provider service. See these topics for guidance managing and configuring your services: * [Manage Email Templates](templatesEmail) * [Notification Service Email Templates](notificationEmailTemplateDetails_r) * [Manage SMS Templates](templatesSms) * [Notification Service SMS Templates](notificationSmsTemplateDetails_r) ## Use Cases The use cases available for Notification services are: * [Update SMTP (email) Notification Service](../../processGuide/topics/c_updateNotificationChannel) * [Update SMS Notification Service](../../processGuide/topics/c_updateNotificationChannel) **Parent topic:**[Branding](../topics/branding) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.