Notifications
Adding an SMTP Notification Provider




Routing Notifications to a Provider




Last updated
Was this helpful?
Portal notifications are configured in two places: an SMTP provider (the credentials for sending mail) under Providers, and Notifications (which use case gets routed to which provider) under its own top-level section.
Go to Providers, select the relevant Provider group, then open the Notifications tab — a category alongside Cloud, Kubernetes, Observability, Incident Management, Source Control, and GRC.

Click Add and follow the same Provider Details → Credentials → Scope flow described in Providers. SMTP is currently the only notification provider type.

On the Credentials step, fill in:
Name* — a label for this credential
SMTP Host* — the mail server hostname
Port* — the SMTP port (commonly 587)
From Address* — the address mail is sent from
Username* and Password* — SMTP auth credentials

Finish the Scope step as with any other Provider, then attach it to the relevant Workspace(s).

Go to Notifications in the sidebar. This page lists each notification use case and how many channels are configured for it.

Click a use case to open it, then + Add Channel.

For each channel, set:
Enabled — toggle the channel on or off without removing it
From Identity (optional) — overrides the SMTP provider's From Address for this use case
Provider* — the SMTP provider to send through

Click Save.

A use case with no enabled channel simply doesn't send anything — there's no default or fallback provider. Today there's a single use case, New User Welcome, sent automatically whenever a new user is created; more use cases will appear here as they're added, with no configuration needed to make them show up.
Last updated
Was this helpful?
Was this helpful?

