Notifications

To set up where OpenLM Platform sends notifications, configure each channel once in the Notification Service. The Notification Service is the shared delivery hub of OpenLM Platform. Other OpenLM apps choose what to notify you about, and the Notification Service delivers their messages through three channels: email, ticketing, and push.

Notifications come from several OpenLM Platform applications: Identity, Identity Alignment (the External Services page of Directory Sync), Alerts, Cloud, and any Custom app. Each of them hands its messages to the Notification Service. A single notification can be delivered through one, some, or all three channels.

Before you begin

Confirm these prerequisites:

• You have an administrator role in OpenLM Platform. Managing notification settings requires it.

To open the Notification Service, select Navigation (the grid icon in the OpenLM Platform header), then Platform Administration, then Notifications.

For related tasks, see Alerts.

How notifications work

A notification is delivered in the following steps:

1. An OpenLM app (for example, an Alerts rule such as "License usage > 90%") raises a notification.
2. The app publishes the notification to the Notification Service.
3. The service delivers it through each channel the notification targets: email, ticketing, push, or any combination of them.

Because delivery is centralized, you configure each channel once in the Notification Service and every OpenLM app reuses it.

Email notifications

To choose who receives test emails from OpenLM Platform and, optionally, how notification subject lines are tagged, open Email Notifications.

The Email Notifications page, with the Test Email Recipients grid and the Advanced section.

Add test email recipients

To add the addresses used to verify the channel:

1. Enter an address in the Email field.

2. Select Add.

   Use the row actions to edit or remove an address.

3. Select Send Sample Email to send a test message to those recipients.

   On success, a message confirms the send: "Email was sent, check inbox please."

4. Select Save.

Sending is managed for you

In hosted OpenLM Platform, email is sent centrally through the OpenLM managed mail service (from no-reply addresses). No Simple Mail Transfer Protocol (SMTP) server fields are available to configure here, so you manage recipients and subject formatting only. On-premises deployments also configure a Sender Account (Sender Email, Host, Port, a Security toggle that reveals the SMTP username and password, and an SSL toggle).

The recipients of a given notification are set by the app that raises it (for example, an Alert's own recipient list). Test Email Recipients are the addresses used when you send a sample email from this page.

Add subject prefixes and suffixes

To add a prefix, a suffix, or both to notification email subject lines, per originating application, expand Advanced. This helps you filter or route OpenLM Platform mail in your inbox or ticketing system.

The Advanced section, with the Prefix/Suffix toggle turned on.

1. Turn on Prefix/Suffix.

2. Select an Application: OpenLM Identity application, OpenLM Identity Alignment, OpenLM Alerts, OpenLM Cloud, or Custom.

3. Enter a Prefix, a Suffix, or both.

4. Select Add.

   Only one entry per application takes effect. If you add more than one for the same application, the first is used.

5. Select Save.

Ticketing notifications

To turn notifications into support tickets, email them to your ticketing platform's inbound email-to-ticket address.

The Ticketing Notifications page, with Ticket System set to EmailSender.

1. Select EmailSender in Ticket System.

   EmailSender is the available delivery method.

2. Add your ticketing platform's intake address under Test Email Recipients (for example, a ServiceNow, Jira, or Zendesk inbound email address).

3. Select Send Sample Email to confirm the address accepts mail.

4. Select Save.

Note

Ticketing delivery is email-only: OpenLM Platform sends the notification as an email that your ticketing platform ingests through its email-to-ticket feature. OpenLM Platform has no direct API or two-way integration, and it does not track ticket status. As with email, on-premises deployments configure their own Sender Account here.

Push notifications

Push delivers real-time alerts to devices that have subscribed to receive them. In OpenLM Platform, push is delivered through Firebase Cloud Messaging (FCM).

Push notification history

To verify delivery and audit what was sent, use the Push Notifications tab. It logs every push notification that has been sent.

The Push Notifications tab, with the history grid and a detail pane.

The tab works as follows:

• The columns are Application, Notification Level (Warning, Info, or Error), and Notification Time.
• Select a row to view its Subject and Message in the detail pane.
• Use the toolbar to Delete a selected notification, Send Sample Push Notification, Refresh the list, or Search.

Subscriptions

The Subscriptions tab lists the devices registered to receive push notifications. Devices are added automatically when they subscribe, so this tab is read-only.

The Subscriptions tab, with the Application, Token, and Subscribed at columns.

The columns are Application, Token, and Subscribed at.

Send a sample push notification

To confirm that subscribed devices receive pushes, select Send Sample Push Notification and complete the dialog.

The Send Sample Push Notification dialog.

1. Enter a Subject (required).
2. Select an Application and a Notification Level (Warning, Info, or Error).
3. Enter a Message (required).
4. Select Send. The sample is delivered to subscribed devices and recorded in the history.