Services

Explore Kyndryl Bridge Services

Administrator-configured notifications
Published On Jun 24, 2026 - 9:13 AM

Administrator-configured notifications

Learn how administrator-configured notifications provide a centralized way to create and manage priority and service-based notifications, define recipients and control key attributes such as status, severity and duration.
The Administrator view provides a centralized interface to configure and manage notifications. Administrators can create and manage priority and service-based notifications to define recipients and control key attributes such as status, severity, and duration. Access is limited to users with administrative permissions, making it the primary entry point for setting up notifications, while end users consume them through the platform interface.
Users with the appropriate Bridge roles can access notification settings through the following navigation path:
  1. Log in to
    Kyndryl Bridge Console
    .
  2. Click on Hamburger menu on the masthead and select
    Administration
    .
  3. Under
    Service Operations
    , select
    Notifications Management
    to open the Notifications Management page.
The following notifications are available:
  • Service-based notification (In-App/Email)
  • Priority notification (In-App)

1. Service-based notifications (In-App/email)

Notification templates define the structure and content of notifications. Templates are centrally managed in a Git repository where application teams contribute, validate templates and build pipeline processes before they are made available across accounts in Kyndryl Bridge Console. They enable administrators and services to standardize how notifications are created and sent, ensuring consistency across the platform. Templates are typically used by applications or services to generate notifications dynamically based on events.
Creating Service-based notifications
Service-based notification templates are configured through a Git-based template, where administrators define whether notifications are delivered via
In-App, email
 or
both
 channels.
  • Define how notifications are structured, triggered, and delivered within the platform.
  • Control notification channels (In-App and email).
  • Control the target audience.
  • Add or remove recipients as needed through the Kyndryl Bridge Console.
Note:
Only users with the
Administrator
role can create Git templates for notifications in the Git repository, ensuring that template creation is performed by an authorized role.
Notifications are created through Git template which contains this information:
  1. Application/Service
    : Enter the application or service from which the notification is generated.
  2. Events:
     Define the events for which the notification is generated. For example, workflow events, manual actions and scheduled jobs.
  3. Title:
     Defines the name of the notification.
  4. Description:
     Add a short description. This is the message displayed in the In-App notification channel along with the notification title.
  5. Severity
    for the notification:
     Defines the priority level of the notification. Available options are
    Critical, Error, Warning, Success
    and
    Info
    .
  6. Type of notification:
     Select the type of notification. If no relevant option is available, users can add a new notification type.
  7. Select Notification Channel:
     Select the notification channel for a particular notification. Available options include
    In-App only
    ,
    Email only
     or
    both In-App and email
     (default selection).
  8. Recipients:
    Define the users or groups who will receive the notification.
    • User-level notification:
      Targeted to individual users or access groups within an account.
    • Account-level notification:
       Broadcast to all users in selected accounts.
    Note:
    If an account-level notification is selected, the notification in the UI is displayed as
    Active
    . If a user-level notification is selected, the notification in the UI is displayed as
    Draft
    .
  9. Links:
     Add links, if required, for direct actions (e.g. “Download report”) . This is not a mandatory field.
  10. Languages
    : Define the preferred language in the template. A total of 12 languages are currently supported for notifications, and the default language is English. This is not a mandatory field.
Note:
If email is selected as a notification channel, the fields shown below must also be completed by the administrator.
Notification template structure
Notifications can be configured using notification templates. Templates are centrally managed in a Git repository, where application teams contribute and validate templates through build pipeline processes before they are made available across all accounts. Email templates should include clearly defined default sections to guide users when setting up notifications.
The following outlines the email notification template structure:
  • Default sender
    : Uses [email protected] as the standard sender address for all email notifications.
  • CC and BCC
    : Allow additional recipients to receive copies of the email notification.
  • Subject line (mandatory)
    : Concise and descriptive, clearly reflecting the purpose of the notification.
  • Salutation
    : Includes a personalized greeting using the recipient’s name or group.
  • Message body
    : Includes the core details of the event or action.
  • Actions:
    Add actions as part of the email, such as: Instructions and direct action links or buttons.
  • Footer Section:
    This section includes the following details: Thank-you note and signature.
Viewing notifications in Kyndryl Bridge Console
Once the template structure is defined, notifications are displayed in the Kyndryl Bridge Console under the Service Notifications tab. In the Notifications Management page, under the Service Notifications tab, a table is displayed to provide an overview of all configured notification templates. This table includes the following columns:
Notification Title, Type, Topic Name, Application/Service, Channels, Languages, Events, Severity
 and
Status.
Follow the steps below to view notifications in the UI:
  1. Log in to
    Kyndryl Bridge Console
    .
  2. Open the
    hamburger menu
     on the masthead and select
    Administration
    .
  3. Under
    Service Operations
    , select
    Notifications Management
    .
  4. Go to the
    Service Notifications
    tab to view the list of notification templates and events, where notifications created using the template described above are displayed.
  5. In the notification title column, select the drop-down arrow to expand and locate the template.
  6. The expanded view displays additional template configuration details in a table format. This table includes the following columns:
  • Event:
     Specifies the trigger associated with the notification (for example, login).
  • Short Description:
    Provides a brief summary or message related to the event.
  • Language:
    Indicates the language configured for the notification (for example, en).
  • Recipients:
    Lists the users or groups who receive the notification.
Editing Service-based notifications
Users can update recipients, delete notifications and download templates. Administrators can add or remove recipients for each notification type, including individual users and access groups, as needed. If users need to modify any other metadata beyond these options, they must make those changes in the Git template.
Follow the steps below to edit service notification:
  1. Log in to
    Kyndryl Bridge Console
    .
  2. Open the
    hamburger menu
     on the masthead and select
    Administration
    .
  3. Under
    Service Operations
    , select
    Notifications Management
    .
  4. Go to the
    Service Notifications
    tab and locate the notification.
  5. In the notification title column, select the drop-down arrow to expand and locate the template.
  6. Select the toggle menu and click
    Edit
    .
  7. On the
    Edit Recipients for Success Event
    page, select the required audience from the recipient list:
  • Entire account
    : Send the notification to all users
  • Access groups
    : Target specific groups of users.
  • Individual users
    : Send the notification to selected users
Enabling and disabling Service-based notifications
Administrators can control whether a notification is active by enabling or disabling its template. This helps manage which notifications are sent to end users and prevents unnecessary or irrelevant alerts.
  1. Go to
    Notifications
     page.
  2. Locate the template (active or disabled).
  3. Select the three-dot menu (More options) next to the template, and choose
    Enable
     or
    Disable
    , as needed.
If you select
Disable
, the template status changes to disabled, and notifications triggered by this template are no longer sent to end users. If you select
Enable
, the template becomes active and notifications associated with this template are sent when triggered.

2. Priority notifications (In-App)

Priority notifications are visible across the platform once created. Active notifications are immediately displayed, while upcoming notifications are scheduled based on configured dates. Users are required to acknowledge these notifications to ensure critical information is received. For Priority notifications, users will see a pop-up prompting immediate awareness and acknowledgment.
The following attributes define the configuration of Priority notifications and control how they are displayed and managed:
  • Title:
     The notification title (maximum 250 characters).
  • Severity:
     Defines the importance level, indicating the urgency and impact of the information by categorizing it as
    Warning,
    Critical
    , or
    Info
    .
  • Duration:
     Define how long the message needs to be retained in the info message table, max 365 days allowed from the current date. These info messages are auto removed after the end date.
  • Status:
     Defines the state of the notification, indicating whether it is
    Active, Upcoming or Draft
    .
Creating Priority notifications from scratch
Follow these steps to create a new priority notification:
  1. Go to the
    Notifications
     page and select
    Manage Notifications
     in the top-right corner.
  2. Select the
    Priority Alerts
     tab.
  3. Click the
    Create Priority Alert
    button in the top-right corner.
  4. Enter the required details (such as title, message content, severity, and duration) to define how and when the notification is delivered.
  5. Click
    Create
     or
    Save for Later
Once saved, users are redirected to the Priority notifications table, where the updated notification is displayed.
Managing Priority notifications
Manage notifications by updating or deleting them after creation. Based on their status and administrator role permissions, administrators can edit details, adjust settings or remove notifications as needed.
Follow these steps to manage Priority notifications:
  1. On the
    Manage Notifications
     page, find the notification you want to manage and review its status (for example, active, upcoming or draft).
  2. After identifying the notification, select the three-dot menu to access available actions. Choose
    Edit
    to update details such as content, severity, or duration or select
    Delete
     if it is no longer needed.
  3. Save
    Click
Viewing and accessing Priority notifications (user view)
The notification pop-up appears on the right side of the Bridge Console. When a user selects Read more, a side panel opens with a quick view of recent notifications, highlighting unread messages and displaying priority notifications until acknowledged to help users quickly understand and act on important updates.
The following actions are available in the Notification pop-up:
  • Acknowledge
     notifications using the available options to confirm or defer review:
    Yes, I read it
     confirms acknowledgment and removes the notification from view.
  • Close all notifications in the panel at once by selecting
    Close All
    .
  • The
    See
    All
    Notifications
     option provides a list of all available notifications.
Modifying existing notification set up
  • Any modification on the notification set up (In-App or Email) can be done by the consuming applications/services via template
  • Platform Admin, Operator and Editor should be able to
    enable
    and
    disable
     the notification from the
    API
    .
Do you have two minutes for a quick survey?
Take Survey