Skip to content
Dashboard
Theme
Theme

Customer IT email

Configure a verified sender and bounded templates for eligible IT notices.

View Markdown

Business and Enterprise environments can configure a customer sender for eligible IT email. Supported providers are SES, Postmark, Resend, Mailgun, SendGrid and SMTP. GET, PUT and DELETE /v1/it_email_configuration read, replace and remove configuration using environment read/write access. Before anything is configured, GET answers 404 resource_not_found; PUT creates the configuration.

Replacement requires the current eligible plan. A downgrade retains existing configuration and delivery; deletion remains available. Credentials are write-only, envelope-encrypted to the environment and an immutable replacement identifier, and absent from public responses.

Create an email custom domain through the custom-domain API and publish its returned ownership, SPF and DKIM records. Explicit verification checks those configured records. The From address must be a bare address on that exact sender domain.

DNS proof is fresh for 24 hours and needs explicit re-verification. Missing, stale, future or invalid proof selects platform defaults. DNS verification is not proof of provider signing, mailbox ownership or actual delivery. Email domains do not grant broker-host or ACS authority.

SMTP requires verified TLS on port 465 or STARTTLS on port 587 before authentication. API providers use bounded, checked public HTTPS requests without redirects.

Customer routing is limited to authorized IT setup invitations and reminders, Doctor instructions, certificate/metadata and IdP-change notices, signing-key rotation and IT health notices.

Developer notifications, dashboard authentication, OTP, MFA, recovery, bootstrap, staff, operator, security and billing mail stay platform-controlled. This configuration does not replace portal authentication mail. Customer failover notices use events and the status page, not customer email.

You can override up to seven templates, one per category: setup_invitation, setup_reminder, certificate_warning, metadata_warning, idp_warning, rotation_notice and health_notice. The only placeholders are organization_name, application_name, connection_name, action_url and expires_at; action_url is not allowed in the subject. A plain-text body is required.

Use only the documented category and literal variables in the API reference. Templates accept a bounded sanitized markup subset. Real action and expiry blocks cannot be removed or substituted with invented values. Callers without truthful action/expiry evidence use the complete platform default.

Input limits are 200 bytes for the subject, 16 KiB for text and 32 KiB for HTML; rendered text and HTML are bounded to 32 KiB and 64 KiB. Invalid or unsupported overrides use the platform default rather than partially rendering unsafe content.

A definite rejection before submission permits one complete platform-default fallback, using the platform sender. Accepted, uncertain and accepted-with-log-error outcomes never resend. A fixed routing marker records fallback without exposing recipient addresses; it is not delivery evidence. Provider submission or an API success response does not prove the recipient received or read the notice.