Gen3 Admin Email Settings
- Open Email Settings.
- Configure SMTP or provider credentials for transactional email.
- Publish tenant support email and portal links tenants see read-only in Account Settings.
- Send a test message after credential changes.
- For broadcasts on v3.0.6-stable, open Compose broadcast, switch the body editor to HTML before entering content, then send — see Broadcasts below.
Tenants display support contacts from this policy; wrong values generate support noise in the tenant app.
Email Settings is the active Gen 3 Control Panel route for outbound email and tenant-visible support policy. It combines SMTP transport, support-contact publishing, welcome-email controls, and broadcast compose/send/review.
Email Templates & Modules is a separate sidebar route documented at Email Templates & Modules. Use that page when you need to create, edit, preview, or delete template bodies and shared modules—not when you are only configuring SMTP or sending a broadcast from Email Settings.
- configuring SMTP host, port, credentials, and TLS posture
- publishing tenant-visible support email and support portal values
- enabling or disabling welcome email behavior
- editing welcome-email copy fields
- selecting welcome and password-reset templates for live email flows
- composing, previewing, sending, and reviewing broadcast records
This is the transport layer. If password resets or welcome emails are not being delivered, start here first.
This section controls what tenant users see under Contact support. It can publish email-only, portal-only, or combined support paths.
Use this section to control whether onboarding email is sent and what subject/body content should be used.
Use the Broadcasts tab to compose audience-targeted messages, attach an existing broadcast template, include optional modules, preview recipients, and send or review broadcast records.
Template and module authoring lives on the separate Email Templates & Modules sidebar route. Email Settings consumes those artifacts when you pick templates for welcome, password-reset, or broadcast flows.
- Open Email Settings and select the Broadcasts tab.
- Click Compose broadcast (or open an existing draft).
- Optionally choose a Template — selecting one fills the subject and body so you can edit before sending.
- Enter the Subject.
- In the Body editor, select HTML in the top-right toggle before you enter or paste broadcast content (see screenshot below). Do not compose in Visual mode first and switch afterward — that path can corrupt formatting on send in v3.0.6-stable.
- Enter or paste your broadcast HTML in the body field.
- Choose the audience (roles, explicit emails, or other filters supported on the form).
- Click Preview recipients to confirm the audience, then Send broadcast (or Save draft to finish later).
On v3.0.6-stable, broadcast emails composed in Visual mode may not render with the intended formatting when sent (for example, line breaks, lists, or inline styling may appear wrong in the delivered message).
Workaround: Before entering any body content, switch the compose dialog to HTML mode and author the message as HTML. Sent broadcasts then render correctly for recipients.
This is a known bug in v3.0.6-stable; a fix is tracked for a future release. Until then, treat HTML-first composition as the required workflow for broadcasts.
- Confirm SMTP works.
- Publish the correct support contact policy.
- Review welcome-email behavior.
- Confirm templates and broadcasts reflect the intended deployment communications.
If a user reports missing email:
- Check SMTP configuration.
- Confirm the welcome-email or password-reset path is actually enabled.
- Confirm the support policy points to the right contact path.
- Return to Users if the underlying user action needs to be re-sent.
- Keep support email and support portal details accurate because they surface directly in the tenant shell.
- Treat SMTP transport and support-contact policy as separate concerns.
- Re-test or re-validate user onboarding after major welcome-email changes.
- On v3.0.6-stable, compose broadcasts in HTML mode before entering body content so sent messages render correctly.