How Student Caring Works

This notification is triggered when a user is assigned their first Awareness or Channel license.

Below are some scenarios, which should be read in order:

Action	Trigger
I create a user and assign a phishing license
I assign a channel license to the same user as above
After assigning the channel license, I also assign the awareness license
At this point, I remove all licenses and then reassign the channel license

This event uses the "user credentials" placeholder, which behaves differently depending on the user's authentication method:

• For users with traditional authentication (not SSO), the placeholder automatically generates a temporary password for first-time login.

• For users who log in via SSO (Single Sign-On), the placeholder instead returns a different static string that does not include login credentials.

This notification is triggered when the very first contentis released to the user, whether it's Awareness or Channel content.

The event is triggered if the first release happens

• Via the calendar in scheduled mode.
• Instant release of individual content using the dedicated button in the release calendar (available for internal Cyber Guru roles).

• If the user has already received the email for the first Awareness or Channel license assignment, the event linked to the first content release of Awareness or Channel type will not generate a new email (the user will have already received the welcome email).

The event is NOT triggered in the following cases:

• Cyber Pills released instantly
• Instant release of the entire course at the time of course assignment (option "release all activities").

Note: 

• If a user is added with the option to align with other users, the content they receive will not be considered their first, since they will already be synced with the group's status.
• On the other hand, if a user is added without alignment, they will start the course from the first available content. In this case, if an instant release is done using the dedicated button, the "First Content" event will be triggered, which can generate an automatic notification to the user.
• Finally, if a user is assigned a prerequisite course (with immediate release of all activities) plus a subsequent standard course with regular scheduled releases, the prerequisite course content will NOT trigger the event (since it was released during course assignment), and it will also NOT be triggered later (when the first scheduled release of the standard course happens), because the system will see that the user already has content assigned.

If new users are added after the course has started (that is, with alignment to other users), it is recommended to use the Student Caring for "First License Assignment".

This way, you can still send a welcome message, avoiding the situation where the “First Content” event is ignored because the initial content has already (or not yet) been assigned.

Sending this email disables the multiple content email for that day only.

This event uses the "user credentials" placeholder: for users with "normal" authentication, the placeholder automatically generates a temporary password. For SSO access, the placeholder returns a different static string, without including credentials.

Below are some scenarios, which should be read in order:

Action	Trigger
For a user with AW and CH licenses, an Awareness content is released at 9:00 AM
On the same day, another Awareness content is released to the same user at 9:30 AM
On the same day, a Channel content is released to the same user at 10:00 AM
The next day, a Channel content is released to the same user at 9:00 AM

This notification is triggered for every release of an awareness content (excluding pills), even if the release is done via the instant release button (available to internal Cyber Guru staff).

The event is not triggered if all course activities are released at the same time as the course assignment.

If multiple releases are scheduled on the same day, one notification will be sent for each awareness release. In other words, the system sends multiple emails on the same day, matching the number of individually released contents.

Note: If a single scheduled release activates multiple contents (e.g., Module + Cup), the event will be triggered as many times as there are contents activated, sending the corresponding number of emails (in the module + cup example, two emails will be sent)

Below are some scenarios, which should be read in order:

Activity	Activation
For a user with AW and CH licenses, an Awareness content is released at 9:00 AM
On the same day, for the same user, another Awareness content is released at 9:30 AM
On the same day, for the same user, a Channel content is released at 10:00 AM
The following day, for the same user, a Channel content is released at 9:00 AM

The event is also triggered if content is released instantly using the dedicated button.

This is triggered every time a Channel-type content is released. The event is not triggered if all activities in a path are released at the same time as the path assignment.

If there are multiple scheduled releases on the same day, a notification will be sent for each Channel-type release. In other words, the system generates multiple emails on the same day, matching the number of individually released contents.

Below are some scenarios, to be read in sequential order:

Activity	Activation
For a user with AW and CH licenses, an Awareness content is released at 9:00 AM
On the same day, for the same user, another Awareness content is released at 9:30 AM
On the same day, for the same user, a Channel content is released at 10:00 AM
The following day, for the same user, a Channel content is released at 9:00 AM

The event is also triggered if content is released instantly using the dedicated button.

The notification is triggered when a remediation-type path is assigned to users marked as targets (in the dedicated Remediation Training section).

It is only triggered when assigning a remediation-type path; in all other cases, it is not triggered.

For example:

• Assigning an Awareness-type path: not triggered
• Releasing a module from a Remediation-type path: not triggered
• Assigning a Phish Pro license: not triggered

This event allows you to send a reminder email to users who have fallen behind in the Cyber Guru Awareness path.

The timing and the number of modules can be customized, as well as the email content.

• The number set as the threshold for incomplete modules that triggers the event should be interpreted as "greater than or equal to."
• The number of days is interpreted as an exact value.

The event also considers inactive users (suspended users are excluded).

In the example, 30 days after the last release, if a user has three or more Awareness modules not fully viewed, they will receive the reminder email.

Example: the last release was on June 4, and you set 23 days for the reminder: on June 27, users receive the email.

This event allows you to send a reminder email to users who have fallen behind in the Cyber Guru Channel path.

The timing and the number of episodes can be customized, as well as the email content.

• The number set as the threshold for incomplete episodes that triggers the event should be interpreted as "greater than or equal to."
• The number of days is interpreted as an exact value.

In the example, 30 days after the last release, if a user has three or more Channel episodes not fully viewed, they will receive the reminder email.

Example: the last release was on June 4, and you set 23 days for the reminder: on June 27, users receive the email.

Notify all students in a certain status (On track, regular, not regular, inactive)

The new Student Caring feature allows you to send automatic notifications (reminders) to students based on their alignment status within the platform.

Each Student Caring is associated with only one alignment status. So, there are a total of 4 events:

• Notify all inactive students
• Notify all not regular students
• Notify all regular students
• Notify all on-track students

For each alignment status, you can:

• Send the reminder to all users in that specific alignment status.
• Send the reminder only to students, in that status, from a specific Organization.

Scheduling the Send

Once Student Caring is set up, you can:

• Schedule the send for a specific date
• You can send a reminder every 7 days for each Student Caring.
• The time limit is tied to the Student Caring itself (that is, to the event), not to the selected Organization.
• As a result, if a reminder for a certain alignment status has been sent (or scheduled) for a specific Organization, you cannot send another one to a different Organization (for the same status) until 7 days have passed.

Note: a Student Caring event that has been executed at least once cannot be deleted. However, you can edit it: if the date is expired at the time of editing, the system will require you to set a new future date before saving changes.

Reminder Content

Each Student Caring uses a message template:

• A default text is available, already translated into many languages
• The reminder text can be customized

• The student caring event, in the case of inactive users, contains a placeholder that is populated as follows:

  • For LDAP/SAML (SSO) users: the {{user_forgot_password}} placeholder is replaced with an empty string, so the message does not appear.

  • For standard users: the message is shown: “If you don't remember your credentials, use the Forgot Password function.”

Language Management

• If a change is made in one language,
• the same change must be manually replicated in all other available languages

Future Developments

New features will be available soon, including:

• Scheduled and recurring sends
• Lower sending limits, to allow for more frequent and targeted communications

These updates will make Student Caring even more flexible and effective.

Initial technical testing phase

We recommend using the "First license association" Student Caring, which immediately sends the user the access link and credentials. This allows you to test both email delivery and correct platform access, without waiting for a dedicated content release.

Go Live phase and subsequent releases

It is recommended to always keep the "First Awareness or Channel content" and "Multiple content" events active. This way:

• Users will receive the welcome email with credentials and access link on the first day (only one email).
• On days when one or more releases are scheduled, they will still receive only one email related to the multiple content event.

It's important to note that users who have already received the email via the "First license association" event will not receive a second email on the day of the first release: the first content event will not trigger again for them.