---
title: "Notifications and Emails"
slug: "notifications-and-emails"
updated: 2026-07-24T08:39:11Z
published: 2026-07-24T08:39:11Z
canonical: "docs.discngine.com/notifications-and-emails"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.discngine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notifications and Emails

# Notifications and Emails

## Overview

The Admin Center keeps administrators informed through **notifications**, delivered two ways:

- **In-app** — under the **bell** in the top bar, with an unread count. Each notification is addressed to a specific person, carries a severity (info, success, warning, error) and, where relevant, links to the page you need. You can mark notifications as read or dismiss them.
- **By email** — for the events that warrant it, the same message is also sent by email, so it reaches you even when you are not signed in.

Notifications are per-recipient: you only see the ones addressed to you.

## What raises a notification

| Event | Who is notified | Channels |
| --- | --- | --- |
| **User import complete** | The administrator who started the bulk user import | In-app |
| **Identity provider secret / certificate expiring soon** | Your organisation's administrators, as expiry approaches | In-app + email |

### User import complete

Bulk user imports run in the background. When an import finishes, the administrator who launched it receives a notification summarising the result, so there is no need to wait on the page.

### Identity provider secret / certificate expiring soon

Identity providers rely on credentials that expire — an OpenID Connect client secret or a SAML certificate. As the expiry date approaches — **30 days, then 7 days before** — your organisation's administrators are notified (in-app and by email), naming the provider and the expiry date, since rotating the credential is their action. Rotating it before it expires avoids a sign-in outage for the affected applications.

## Severity

Severity is a hint about how much attention a notification needs — *success*, *info*, *warning* (an approaching expiry) or *error* (an imminent one). It sets the colour and icon shown in the bell; it does not change who receives the notification.

## Emails the Admin Center sends

Beyond the in-app notifications above, the Admin Center sends a few transactional **emails**:

| Trigger | Email | Sent to |
| --- | --- | --- |
| A user gains **first access** to an application (a licence assignment opens an application they did not have before) | Welcome to *<application>* | The user |
| **30 / 7 days before** an identity provider secret or certificate expires | Identity provider secret expiring soon | Your organisation's administrators |
| A **local user is created**, or a **password reset** is requested | Set / reset your password (secure link) | The user |

Email delivery is best-effort: if the mail service is briefly unavailable, the in-app notification is still created and the underlying action always completes.

## Related

- [Access Roles](/public/docs/access-roles) — the administrators who receive these notifications
- [How to Manage Identity Providers](/public/docs/how-to-manage-identity-providers) — setting a secret / certificate expiry date