> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.superpath.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Certificate Expiry Notifications

# Certificate Expiry Notifications

**In this article:**
* Overview
* Who gets notified?
* How to configure expiry notifications
* Notification timing
* Things to keep in mind
* FAQs
* Who can do this

## Overview
Certificate Expiry Notifications let you configure who receives a notification when a user's Certificate is approaching its expiry date. This means Managers and compliance teams stay informed, not just the individual learner.

This setting is configured per Certificate and can include Managers, specific users, or entire Teams.

${frame}[](https://www.loom.com/embed/f32efb5208434e7a9c787c4683d8b7e1)


## Who gets notified?
By default, the learner who holds the certificate receives expiry reminders automatically. With this feature, you can extend notifications to additional recipients:
| Recipient type | How it works |
| ---- |
| **Manager** | The direct manager of the certificate holder is notified automatically |
| **Individual users** | Specific people from your organisation added by name |
| **Teams** | All current members of a selected team are notified |

## How to configure expiry notifications
1. Go to **Settings → Features → Certificates**
2. Open the certificate you want to configure
3. Scroll to the bottom of the certificate settings page
4. Under **"Who do you want to notify on expiry?"**, select your recipients
5. Click **Update** to save

![](https://storage.crisp.chat/users/helpdesk/website/-/c/0/6/4/c0645e580ffc0800/image_qxqht2.png)


## Notification timing
Notifications are sent at set intervals before a Certificate expires:
* **90 days** before expiry
* **60 days** before expiry
* **30 days** before expiry
All configured recipients, including the learner, receive notifications at each of these intervals.

## Things to keep in mind
**Use a Team, not individuals.** We strongly recommend adding a Team (such as your compliance Team) as the notification recipient rather than listing individuals:
* When someone joins or leaves your compliance Team, the notifications automatically reflect the current membership — there's no need to update each Certificate individually.
* Individual recipients have to be updated manually across every Certificate if someone leaves the organisation or changes roles.

**Combine recipient types.** You can use a combination of recipients on a single Certificate — for example, notify the learner's Manager *and* your compliance Team. Both receive notifications at the standard intervals.

## FAQs
**Do I need to configure this for every Certificate?**
Yes — expiry notification recipients are set per Certificate. If you want consistent notifications across all Certificates, you'll need to configure each one individually.

**What if the Certificate holder doesn't have a Manager set up in SuperPath?**
If the "Notify manager" option is enabled but no Manager is assigned to the user, that notification won't be sent. Make sure your user profiles have Managers configured if you're relying on this option.

**Will existing Certificate holders trigger notifications once I save these settings?**
Yes — once configured, any Certificate holder whose expiry falls within the notification window will receive reminders at the next scheduled interval.

**Can I add someone from outside my organisation?**
No — recipients must be users within your SuperPath organisation.

## Who can do this
Certificate settings live under **Settings → Features → Certificates**, which only **Owners** and **Admins** can open, so they are the roles who can configure expiry-notification recipients. Although some Manager roles hold Certificate permissions elsewhere in SuperPath, **Managers**, **Content Managers**, **People Managers**, **Instructors**, **Employees** and **Restricted** users cannot reach these settings because they can't access the Settings area.