import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';

Welcome user email

Overview

The welcome user email is sent when a user successfully registers for your application. It acknowledges the sign-up and introduces the portals and resources the user can access with their new account.

Key benefits

• Confirms successful user registration
• Introduces login access and portals
• Improves first-time user experience

Admin perspective

The welcome user email is managed under Communication Management under template key WELCOME_USER.

That template type is deactivatable, but the pre-seeded email and SMS templates in the default group start disabled. To send the welcome message, open Template > Template, enable the WELCOME_USER templates for the locales and channels you need (at minimum email), customize content if required, and publish them.

See Template activation defaults for how deactivatable and enabled interact across all system templates.

---

Details and configuration

info

If your application requires email or mobile number verification, the welcome user email is sent only after the account is verified.

Configuration criteria

Criteria	Description	Configuration
Activation / deactivation	WELCOME_USER is optional: you can disable the template type because it is deactivatable. Pre-seeded email and SMS rows in the default group are disabled by default—enable and publish them before users receive a welcome message. Core flows (for example verification or password reset) use templates that are enabled by default.	Communication Management
Account verification	If verification is enabled, users must verify their account using OTP or a verification link before the welcome email is triggered.	—

The login link is a dynamically generated parameter included in the welcome user email.

• The primary login link is derived from app.initiate_login_uri.
• As a fallback, cidaas reconstructs the authorization request to generate a login link.
• The fallback mechanism works only if state, nonce, or code_challenge (PKCE) are not used.
• In fallback scenarios, the login link may be shortened.

The login link can be:

• Embedded in a button, or
• Displayed directly as linked text in the email template.

The triggered email includes a to parameter that defines the recipient of the email.

• The login_link is passed as metadata.
• You can reuse the provided html and subject fields.
• The email can be sent using your own email provider.

Example payload

{
  "from_email": "[email protected]",
  "from_name": "noreply cidaas",
  "to": "[email protected]",
  "subject": "Welcome to the amazing Demo Introduction",
  "html": "<PLACEHOLDER>",
  "accept_language": "de",
  "metadata": {
    "name": "Pocahontas Disney",
    "login_link": "https://demo.cidaas.eu/login",
    "account_name": "demo-test",
    "templateKey": "WELCOME_USER"
  }
}

---

Explore related topics

• Communication Management overview
• Communication templates and activation defaults
• Account verification settings
• Custom email providers

---

Support

Need Help?

For any further assistance, feel free to visit our Support Portal.