Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring Pulse email notifications

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

In Pulse, you can choose to receive emails when another user references you, likes your messages, posts on your profile, posts comments on a conversation in which you are involved, or posts a comment on a case that you are following, provided that your application is configured to send emails.

In addition to receiving email notifications, you can continue a Pulse discussion that was initiated by email. When you reply to a message that is denoted by the Email icon, your post and attachment, if any, are added to Pulse and sent to the relevant user in an email message.

The following tasks can help you configure email notifications for Pulse:

  • Configuring an email account for Pulse notifications

    In Pulse, users can choose to receive email notifications when posts are made on cases that they are following. They also receive emails when other users reference them in posts, like their posts, and so on.

  • Enabling users to respond to Pulse email notifications

    Users can receive Pulse emails on cases that they are following and for which they choose to receive notifications. Users also receive emails when other users reference them in posts or like their posts. You can allow users to quickly post attachments or text as replies by responding to emails instead of logging in to the application.

  • Configuring Pulse notifications on additional email accounts

    After you create the PulseNotifications email account that is used to send Pulse notifications, you can configure individual email accounts for each application for which you want to send Pulse notifications.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us