Notifications
This page provides technical details for configuring and managing MTG CLM’s notification system, including subscription management, contact configuration and event handling.
Understanding Subscriptions
Realm vs Policy Subscriptions
Subscriptions can be configured at two levels with different notification scope:
- Realm Subscriptions
-
Subscribe to all certificate events within an entire realm. Since realms contain multiple policies, this provides broad coverage for all certificates issued using any policy within that realm.
- Policy Subscriptions
-
Subscribe to certificate events for a specific policy within a realm. This provides targeted notifications only for certificates issued using that particular policy.
The subscription process is identical for both levels; the only difference is the scope of events you receive. Policy subscriptions offer more granular control when you need notifications for specific certificate types or use cases.
Subscription Management
User Self-Subscriptions
Users can subscribe themselves to any realm or policy they have permission to view.
User actions:
-
Subscribe to realms or policies
-
Configure notification channels and language preferences
-
Edit subscription event types
-
Delete subscriptions when no longer needed
Default behavior: All users automatically receive email notifications for certificates they have requested.
Administrative User Management
MTG CLM Administrators can subscribe other users based on organizational requirements and permission hierarchies.
Administrative actions:
-
Subscribe users to realms or policies
-
Manage existing user subscriptions
-
Edit and delete user subscriptions within permission boundaries
-
Ensure comprehensive notification coverage across teams
For users with elevated permissions, MTG CLM provides sophisticated tools to orchestrate notifications across your organization, managing both application users and external recipient contacts with precision and security.
Permission-Based Subscription Architecture:

Contact Management
Notification Channels
Notification System Components
The MTG CLM notification system consists of the following business entities interacting with each other:
- Notification Channel Types
-
Defines the different types of supported notifications.
- Notification Event Types
-
Defines the events that may lead to a notification being sent. There are two event types :
-
Subscribable
-
CERTIFICATE_REQUEST_PENDING_APPROVAL
-
CERTIFICATE_REQUEST_APPROVED**
-
CERTIFICATE_REQUEST_DECLINED**
-
CERTIFICATE_CREATED**
-
CERTIFICATE_IMPORTED
-
CERTIFICATE_EXPIRING**
-
CERTIFICATE_REVOKED**
-
-
Non-subscribable
-
CERTIFICATE_ATTACHMENT
-
CERTIFICATE_REQUEST_PENDING_EMAIL_VERIFICATION
-
-
On top of "subscribable" some events may also be "variant". When providing these event types, additional data dictating that period are required. |
**Implicit Notifications: Users can be notified for status changes in a certificate they requested without explicitly subscribing to it. Users can either choose to further configure all event types or a subset of them, according to their specific needs. |
- Notification Languages
-
Defines the language being used in template details. The available languages are:
-
English - en
-
German - de
-
- Notification Templates
-
Defines the contents of a notification. You can find out more here
- Contacts
-
Contains recipient details.
- Notification Subscriptions
-
Contains the subscription details.
- Notifications
-
Contains every data needed to attempt to deliver the notification.
Notification Related Properties
Property |
Description |
|
Defines how many times the notification creation jobs will execute in case of failures. |
|
The interval, in hours, between a failed execution of a notification creation job, and the next execution of it. |
|
Defines how many times the notification processing jobs will execute in case of failures. |
|
The interval, in hours, between a failed execution of a notification processing job, and the next execution of it. |