Configuration

If you have not read it yet, start with Introduction.

Email is configured entirely through the Settings module. Operators use the Admin Panel to enable email, choose a provider, enter credentials, and edit message templates. Values are stored with the rest of Settings (not in client appsettings.json).

Provider

DevKit supports Mailgun, SendGrid, and self-hosted SMTP as email providers. In the Admin Panel you pick one active provider and enter only that provider’s credentials (each provider has its own fields). Additional providers may be added later in the same place.

Settings — Tutorials: Email walks through enabling email and mapping provider-specific settings in the Admin Panel.

Templates and built-in modules

Some prebuilt modules use the built-in email service to notify users by message. For example, Identity sends email for flows such as email confirmation and two-factor authentication, Payment sends order confirmations, and Subscription sends lifecycle messages such as renewal and reminder emails. Those modules do not embed fixed message text in code for those notifications; they resolve content from email templates (and matching subjects) you maintain in the Settings module.

In the Admin Panel, open Settings and use the Email section. There you configure email-related options and edit the templates those modules use when they send a message. Adjust wording, placeholders, and subjects so notifications match your product and tone.

Templates and provider fields are maintained per language (culture)—pick the language in the Admin Panel, edit Email for that culture, then repeat for each language you support so messages match what your users expect.

See also

• Services — IEmailService method signature.
• Tutorials — Sending a custom email from code.
• SaaS template — Configuration — What lives in appsettings.json (email provider credentials do not).