Templates

The Templates hub is the single home for your organization’s reusable templates. It has two sections:

• Certificates — the title, body, and signatory printed on issued certificates.
• Email — overrides of the built-in notification emails (subject + HTML), per language.

Certificate templates previously lived under Courses → Certificates. They now live here. The old link redirects automatically.

Open the Templates hub

1. In the sidebar, click Templates (admin section).
2. Use the Certificates / Email tabs at the top to switch sections.

You only see the tabs you have permission for.

Insert variables with the glossary

Both certificate body text and email templates support variables — placeholders written as {{token}} that are replaced with real values when the certificate is issued or the email is sent.

To add one:

1. Click your cursor where you want the value to appear.
2. Click + Add variable above the field.
3. Pick a variable from the list. It is inserted at the cursor as {{token}}.

Each variable shows its name and a sample value. Unknown tokens (typos) are left as-is so you can spot them.

Certificate templates

Certificate templates define what appears on the issued PDF.

Configuration reference

Certificate variables

A course or learning path picks its template (or the default) in its own editor.

Email templates

Each notification type ships with a built-in, bilingual email. You can override any of them with your own subject and HTML — per language — without touching the built-ins.

How overrides work

• Pick a notification type from the list, then edit the English and Français (CA) versions independently.
• When no override exists, the subject and HTML body are pre-filled with the built-in template (in {{variable}} form), so you start from what learners actually receive and tweak from there.
• An override applies only when Use this override is checked. Uncheck it to keep your draft saved but fall back to the built-in template.
• Reset to default removes the override entirely and puts the built-in template’s content back into the fields; the built-in email resumes.
• A type with any saved override shows a custom badge in the list.

Live preview

A Preview panel at the bottom of the editor renders, as you type, the email that will actually be sent for the selected type and language, using sample values for every variable:

• With Use this override checked, it shows your custom subject and HTML.
• With it unchecked, it shows the built-in email.

Both are shown exactly as your learners receive them: inside your organization’s email frame (see below), with your own logo and button colour.

Three notification types — Quiz passed, Assignment due soon, and Assignment overdue — have no built-in email: by default learners only see an in-app notification. For these, the preview says so, and an email is sent only once you save and enable an override.

Links in the preview are inactive. The panel is a rendering of the email, not a working inbox — the URLs in it are sample values, and following one would replace the preview with a page that cannot be displayed. Clicking a link does nothing; the styling is exactly what the recipient sees. To check where a link points, read its href in the body HTML, or send yourself a real notification.

Your branding in every email

Every email your organization sends to its learners, instructors and managers (the built-in ones and your overrides alike) shares one frame:

• Your logo at the top (set under Settings → Branding). With no logo set, your organization’s name appears there instead.
• Your primary colour on the single action button. If that colour would make the button text hard to read, the text switches between white and near-black automatically, and a colour no text can be read on is darkened slightly, so every button stays readable (WCAG AA).
• Your organization’s name in the footer, under the “why you received this” line.

Your override supplies only the body: the frame adds the logo and footer around it, so you do not need to repeat them. An override written as a complete HTML page (with its own <html> or <body> tag) is sent exactly as written, without the frame.

Configuration reference

Available variables

Variables differ by notification type (the + Add variable menu always shows the correct set). Common examples:

Troubleshooting