Administrator configured notifications

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 from the main menu , go to administration → notifications management the following notifications are available service based notification (in app/email) priority notification (in app) service based notifications set up (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 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 application/service enter the application or service from which the notification is generated events define the events for which the notification is generated for example, workflow events, manual actions and scheduled jobs title defines the name of the notification description add a short description this is the message displayed in the in app notification channel along with the notification title severity for the notification defines the priority level of the notification available options are critical, error, warning, success and info type of notification select the type of notification if no relevant option is available, users can add a new notification type 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) recipients define the users or groups who will receive the notification account level notification broadcast to all users in selected accounts user level notification targeted to individual users or access groups within an account 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 links add links, if required, for direct actions (e g “download report”) this is not a mandatory field 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 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 noreply\@bridge kyndryl com 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 service based notification set up 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 from the main menu , go to administration → notifications management → service notifications view the list of notification templates and events, where notifications created using the template described above are displayed in the notification title column, select the drop down arrow to expand and locate the template 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 from the main menu , go to administration → notifications management → service notifications in the notification title column, select the drop down arrow to expand and locate the template select the toggle menu and click edit 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 go to notifications page locate the template (active or disabled) 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 priority notifications set up (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 from the main menu , go to notifications → manage notifications → priority alerts click the create priority alert button in the top right corner enter the required details (such as title, message content, severity, and duration) to define how and when the notification is delivered 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 on the manage notifications page, find the notification you want to manage and review its status (for example, active, upcoming or draft) 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 save click viewing priority notification set up administrators can review existing priority notification configurations and verify notification details follow these steps to view priority notifications you have created from the main menu , go to notifications management → priority notifications the view all priority notifications takes users to the priority notifications details page, where they can view current priority notifications as well as previously received 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