Required Courses
Before you start
Required Courses is not available to subscriptions using LTI to manage courses through an external LMS.
You must be an Organisation Admin to configure course settings.
Enabling Required Courses
- Go to Edit Organisation and open the Supported Courses section.
- Each course in your subscription is listed with a dropdown to set its status.
- Save your changes. Settings take effect immediately.
Enabling at least one Required course also activates the Compliance report.
Course status options
The available options depend on the course type.
Status | Skills Awareness courses | Short Courses |
|---|---|---|
Default | ✓ | ✓ |
Required | ✓ | ✓ |
Optional | ✓ | ✓ |
Not Offered | — | ✓ |
Skills Awareness courses cannot be set to Not Offered.
All courses are set to Default when your subscription is first configured.
What each status means:
Default — When no courses are marked Required, Default shows the course on users' dashboards with no due date, which is standard behaviour. Once at least one course is marked Required, Default behaves the same as Optional.
Required — The course is mandatory for all users. A due date is calculated and assigned automatically. Users' dashboards switch to a Required/Optional layout whenever at least one course carries this status.
Optional — The course appears on users' dashboards and they can complete it at any time, but there is no due date and no compliance tracking.
Not Offered — The course is hidden from users' dashboards and excluded from admin reports.
How due dates are calculated
When you set a course to Required, the system uses the Required Completion Time from your organisation settings to calculate each user's due date.
- Existing users: due date is calculated from the date you save the Required setting.
- New users: due date is calculated from the date they are invited.
Due dates are calculated using each user's own timezone, and users have until the end of that day to complete the course.
Email notifications and reminders
Users receive emails automatically based on their course status and progress. No manual setup is needed.
When a course is first marked Required: Users receive an email notifying them they have a required course and stating their due date.
Reminder schedule (Required courses only):
- 7 days before the due date
- 3 days before the due date
- On the due date
- 7 days after the due date, if still incomplete
Reminders are only sent to users who have not yet completed the course. No reminders are sent for Optional courses.
Examples
Running a Skills Awareness refresher cycle
You want Skills Awareness to be completed once every three years, with the refresher courses available but not mandatory.
Course | Status |
|---|---|
Skills Awareness (1) | Required |
Skills Awareness (2) | Optional |
Skills Awareness (3) | Optional |
Users are notified of the requirement and see Skills Awareness (1) in their Required section with a due date. They receive reminders as the due date approaches. Skills Awareness (2) and (3) appear in the Optional section and are available to complete at any time.
Phasing in courses over time
At launch you want to focus users on three courses, with others to be introduced later.
Course | Status |
|---|---|
Skills Awareness (1) | Required |
Speed | Required |
Distraction and Inattention | Required |
All other courses | Not Offered |
Users see only the three required courses. This keeps the initial experience focused and avoids confusion about what's expected. You can move additional courses from Not Offered to Required or Optional as your rollout plan progresses.