Customisation Options
We provide generic email templates in HTML for various triggers in the user journeys. For example, an email is automatically sent to a user’s email address when they register their account or reset their password. You can freely customise these templates so that your users receive emails whose content, style, and imagery match your organisation’s identity.
The HTML templates can contain variables to personalise your email with. This enables you to include customer-specific profile data in the automated email. The data you want to include must be present in our database at the moment the email is generated.
Types of Email Templates
Templates to Manage User Accounts
| Email Trigger | Process Description |
|---|---|
| The user changes their primary email address through the credential API. | A first email is sent to the new email address to confirm the new email address. After that, another email is sent to the old email address, notifying that the primary email has been updated. |
| The user initiates a primary phone number change through the Credential API. | A notification email is sent after the primary phone number has been changed successfully. |
| A new (INACTIVE) account is created. | An activation email with a link is sent to the user. The user follows the link in this email to complete the profile completion process. |
| The user wants to log in using the smart link email. (The smart link module is optionally included on the login page.) | An email with a one-time login link is sent to the user, which they have to click to log in. |
| The user wants to log in using OTP verification. | A one-time password (OTP) verification email is sent to a user’s device (e.g. their phone). For 2nd Factor authentication, the user can receive an OTP on their email address if enabled. |
| The user starts the process to retrieve their lost password. | A first email containing a reset password link is sent to the user’s email address. Following the link, the user is redirected to a page to set a new password. After that, another email is sent to the user confirming the password has been changed. |
| The user deletes their account. | Two different flows exist for account deletion: Hard delete - After a user confirms that they want to delete their account, they receive an email that informs them that their account has been deleted. DPO flow - After a user confirms that they want to delete their account, an email is first sent to the data protection officer (DPO). After the DPO has taken the necessary steps and confirms the deletion, the user receives an email that informs them that their account has been deleted. |
Invitation Templates
| Email Trigger | Process Description |
|---|---|
| An invitation is made. | An email is sent to the invitee containing a link to register a new account or log in with an existing account. |
| The invitee accepts the invitation (by clicking 'accept invite' in the invitation email). | An email is sent to the inviter confirming that the invitee has completed the process in the invitation email. |
| The invitee declines the invitation (by clicking 'decline invite' in the invitation email). | An email is sent to the inviter stating that the invitee has declined the invitation. |
| The invitation email sent by the inviter has expired. | An email is sent to the inviter stating that the invitation they sent has expired. |
Other Templates
| Email Trigger | Process Description |
|---|---|
| Someone tries to register an account using an existing email address. | An email is sent to the user with that existing email address. This email notifies the user that someone tried to register an account with their email address. |
| The user clicks on the 'obtain your personal data' link on the self-service page. | An email containing a zip file is sent to the user. This zip file contains the user’s data gathered from the IDAAS core, in compliance with the GDPR. |