| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Configure emails that are sent to your users.
Welcome
...
emails
Upon receiving their initial platform invitation to the platform, they'll be greeted , users are welcomed with an email guiding them through the setup process. This guide is designed caters specifically for clients like you, who don't currently use to clients not currently utilizing Single Sign-On (SSO).
SSO Cases
Before we proceed, let's confirm whether your user base falls into the category of clients who don't have SSO enabled.
Available Routes: You However, we offer options for both SSO and non-SSO users.
For SSO Users:
If you utilize SSO, you have two options for configuring the welcome email system when using SSO:
Fusion Auth Integration (SSO Tie-In):
While this integration isn't active yet, it's our recommended approach. We'll work together to seamlessly integrateThis recommended integration streamlines the process by seamlessly integrating Fusion Auth with your platform's SSO functionality
, streamlining the process of sending welcome emails.
Sendgrid Integration: Alternatively, you can leverage the existing Sendgrid integration
already built intowithin the platform.
If you choose this route, we may need to implementNote that this option may require a transition period of
aroundapproximately one month.
| Info |
|---|
Customization Options For SSO You also have the option flexibility to integrate personalized email tags, allowing you to customize for customized welcome emails according tailored to your preferences or needs and focus on specific usersspecific user groups. |
For Non-SSO Cases
In most instances where SSO isn't utilized, users are typically imported into the system at predefined intervals. Subsequently, a trigger event initiates the sending of welcome emails to all users imported during that period. This process is often facilitated by utilizing tags.
...
To automate the distribution of welcome emails to non-SSO users, we employ utilize a scheduled task that runs at regular intervals, such as every 15 minutes. This task, managed Managed by our team, this task checks for new users until a specified cutoff date, ensuring that prompt delivery of welcome emails to all relevant users receive their welcome emails promptly.
Below is a list of example Emails with Elements, Options, Recommendations, Configurable Default Text, and Full Please refer to the list below for detailed examples of welcome emails, including elements, options, recommendations, configurable default text, and full HTML.
Welcome emails
...
An example welcome email. See the table below for details.
Element | Options | |
|---|---|---|
1 | From name |
|
2 | Subject |
|
3 | Design |
|
4 | Message |
|
Add your organization's name so that users know it’s from you. In most cases, we recommend changing only the “From” name instead of the “From” address. 
Change the text to match your brand voice, and/or add additional information. See the default text and full HTML below....
Users get this email when they request a new magic link.
...
An example new magic link email. See the table below for details.
Element | Options | |
|---|---|---|
1 | From name |
|
2 | Subject |
|
3 | Design |
|
4 | Message |
|
...
Users get this email when they are added as an admin for a content page. Since they now have editing privileges for that page, a link in the email takes them directly to the page editor. This email is not configurable.
...
An example admin email.
Courses
Course enrollment or waitlist email
...
You can configure:
Element | Options | |
|---|---|---|
1 | From name |
|
2 | Design |
|
| Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
These emails will be available again once this is complete:
Forum and feed emails There are a few types of emails that notify users about the latest forum and feed activity, Forum digest email
The forum digest delivers new forum content to users' inboxes. All content in the email is from the previous week or month. Users are automatically subscribed if your platform includes a forum. But that doesn’t mean everyone gets an email every week. Instead, the email is only sent if there is:
If there is no relevant activity, the user doesn’t get an email that week. Someone who never interacts with the forum will never see the digest email.  An example forum digest email. See the table below for details. The email content includes:
Configure these elements:
Real-time forum and feed activity emails Users get these emails right away when one of these activities happens in the forum or feed: In the forum:
In the social feed
Direct message emails There are a few types of emails that are sent to let users know they have direct messages waiting for them on the platform. Direct message request email Users get this email the first time a new person messages them. The email includes a link to their messages and the option to unsubscribe from direct message request notifications.  The subject line automatically pulls in your platform’s name (the “social title” that appears on browser tabs). Beyond that, you can configure:
Direct messages email Users get this email when they receive new direct messages after the initial request. It’s sent once a day, but only if they have new messages. The email includes the names of the senders and how many new messages they sent. There is a link to their messages and the option to unsubscribe from direct message notifications.  You can configure:
One-on-one meeting emails There are a few types of emails sent for a meeting. This could be a meeting between two attendees or between an attendee and an exhibitor. Meeting invite email Users get this email when they are invited to a meeting.  An example meeting invite email. See the table below for details.
Created a meeting email The user who scheduled a meeting gets this email.  An example meeting creation email. See the table below for details.
Meeting time changed email When someone changes a meeting time, both the meeting creator and invitee get this email. 
Meeting cancelation email Users get this email when a private meeting is canceled. It could be a meeting between two attendees or between an attendee and an exhibitor.  An example meeting cancelation email. See the tables below for details.
Or, you can remove cancelation emails:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Don’t send email notifications when meetings are canceled.