Email and app notifications

Cloudgate provides shared app-user email settings and persistent in-app notifications. Choose the channel that fits the message and verify the recipient scope before sending.

Configure email#

Open Web Apps → Email Settings to configure custom SMTP and the email template. Custom SMTP is optional; when it is disabled, app-user email uses the platform delivery configuration.

These settings apply across the tenant's apps and sandbox/production identity flows. Changing them for one app can affect other app-user messages.

Review the sender name and address, server, port, TLS settings, and authentication. Saved SMTP passwords are not returned as readable values. An omitted or empty password preserves an existing secret; use the explicit clearing control when you intend to remove it.

Verify delivery#

Use the available test or a controlled identity flow with a dedicated recipient. Check delivery and the appearance of links, branding, and text. Saving SMTP settings does not itself prove an email can be delivered.

If delivery fails, confirm the sender configuration and provider restrictions before repeatedly triggering user messages. Do not copy an obsolete app-local SMTP configuration over shared tenant settings without reviewing its scope.

Send app notifications#

Use Web Apps → App Notifications for persistent messages to app users and recipient/read information. A workflow can also send a message through the IdP Notification node.

Choose all users or a specific user, then supply a title, body, optional action URL/label, and style. Start with a test user and verify that the link opens the intended app location.

Keep channels distinct#

An app notification is not an email delivery receipt. A WebSocket message is a transient live event. Support-ticket correspondence uses its own ticket communication flow. Check the specific channel's status when investigating a missing message.

See specialized nodes and support tickets.