How to Track Course Deadline Notifications

Last updated Jul 4, 2026

Summary

This article explains how learners see and use course deadline notifications in the Portal Notification Center, what triggers each notification, what the messages look like, and what happens when a learner clicks them.

Introduction

Course deadlines help learners stay on track. The Portal shows timely in‑app notifications for due dates and end (access close) dates, mirroring the emails sent from the LMS. Understanding these notifications ensures learners don’t miss critical training windows.

Requirements

Student has an active Portal account and a valid email set in User profile.
Notifications are enabled for users.
The course is assigned to the student.

Steps to Follow

How Learners View Notifications

To view notifications, open the Portal and locate the bell icon in the top header. A dot or badge appears on the bell when new notifications are available.
Click the bell to open the Notification Center. New notifications appear at the top, followed by older ones below.
Select any notification to be directed to the related page, such as a Course or Learning Path. The notification list refreshes according to Portal refresh rules: approximately every five minutes, or hourly for inactive tabs. Clicking the bell also triggers a manual refresh, provided at least five minutes have passed since the last update.

1) Course Due Date Approaching

Trigger: This notification is sent when an admin has set a due date for a course.
What the learner sees: A Portal notification alerting the learner that a course due date is approaching. The notification includes the course title.
On click: The learner is directed to the relevant Course page to continue learning or review the requirements.

2) Course Due Date Passed

Trigger: This notification is sent when a configured course due date has passed. The system generates a "Due Date Passed" notification according to the background job schedule.
What the learner sees: A Portal notification informing the learner that the course due date has passed.
On click: The learner is directed to the relevant Course page to complete any pending work, provided access is still open.

3) Course End Date Approaching (Access Closing Soon)

Trigger: This notification is sent when an admin has set an end date for a course, after which access will close.
What the learner sees: A Portal notification warning that access to the course will close soon.
On click: The learner is directed to the relevant Course page to complete their learning before access closes.

4) Course End Date Passed (Access Closed)

Trigger: This notification is sent when a configured course end date has been reached. The system generates an "End Date Passed" notification according to the background job schedule.
What the learner sees: A Portal notification informing the learner that access to the course has closed.
On click: The learner is directed to the relevant Course page. If access is closed, the page reflects the locked state according to product rules.

Expected Result

Learners reliably receive in‑app notifications in the Portal for upcoming and passed due/end dates. Clicking the notification opens the relevant Course page so they can continue, complete, or understand access status.

Troubleshooting

Problem	Likely Cause	Fix
No notifications appear in Portal	Notifications disabled at account level Background job window not yet reached Student email missing	Enable LMS → Settings → Account settings → Notifications. Confirm student has an email in LMS profile. Allow several minutes for background jobs; click bell to refresh.
Learner didn’t receive “Approaching” reminders	Due/end date too close to current day Last‑sent safeguards prevent duplicate sends on same day	Verify due/end dates are at least 1 day ahead for reminders. Check that “Notify users” was enabled when scheduling.
Upon click it opens wrong page or blank page	Assignment removed Course archived Permissions changed	Confirm learner still has the course assigned and accessible. If archived, confirm expected archive behavior with Admin.