{"id":7277,"date":"2025-08-08T13:40:10","date_gmt":"2025-08-08T13:40:10","guid":{"rendered":"\/agile\/?post_type=ht_kb&p=7277"},"modified":"2025-08-08T13:43:46","modified_gmt":"2025-08-08T13:43:46","slug":"express-imp-portal_admin-department-notifications","status":"publish","type":"ht_kb","link":"\/agile\/knowledge-base\/express-imp-portal_admin-department-notifications\/","title":{"rendered":"Express Imp. Portal_Admin-Department Notifications"},"content":{"rendered":"\n

\n The Department Notifications<\/strong> section allows the user to configure and manage notifications at a more granular level, either by Department<\/strong> or Role<\/strong>. This feature ensures that alerts and updates reach the appropriate users based on their departmental affiliation or organizational role, enhancing operational efficiency and targeted communication.\n<\/p>\n\n\n\n

Notification Mode Selection<\/em><\/h4>\n\n\n\n

<\/p>\n\n\n\n

\n At the top of the page, users can choose how they want the notifications:\n<\/p>\n\n\n\n

    \n
  • Department-Based<\/strong> (default): . Department notifications will send the notification to the selected user in that department.
    <\/li>\n\n\n\n
  • Role-Based<\/strong>: Role based notifications will send the notification to the supervisor(s) who have visibility to the employees department, and\/or the administrator
    <\/li>\n<\/ul>\n\n\n\n

    NOTE: Only one notification model is active at a time. <\/em><\/strong>\n<\/p>\n\n\n\n

    <\/p>\n\n\n\n

    \"A<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Department Notifications<\/em><\/h4>\n\n\n\n

    <\/p>\n\n\n\n

    \n The Departments<\/strong> panel displays a tree structure of all available departments. This enables users to select a specific department to manage or view its notifications.\n<\/p>\n\n\n\n

    <\/p>\n\n\n\n

    Assign department notifications to users<\/h5>\n\n\n\n

    <\/p>\n\n\n\n

      \n
    1. Upon selecting a department, the Notifications<\/strong> panel on the right displays.
      <\/li>\n\n\n\n
    2. Click \u201cAdd Notifications\u201d



      \"A<\/figure><\/li>\n\n\n\n
    3. Select the user

      \"A<\/figure><\/li>\n\n\n\n
    4. Select the notification type user wants to trigger
      <\/li>\n\n\n\n
    5. Click \u201cSave\u201d



      \"A<\/figure>
      <\/li>\n\n\n\n
    6. It will successfully assign the selected notification alerts to the selected admin user for the selected department.
      <\/li>\n\n\n\n
    7. <\/li>\n<\/ol>\n\n\n\n

      NOTE: <\/em><\/strong>\n<\/p>\n\n\n\n

        \n
      1. You can set only one user for the Absence Request Approver notification. However, for other notifications, user can set multiple approvers\/notifiers.<\/em><\/strong>
        <\/li>\n\n\n\n
      2. On Bolt, we no longer support notification type \u201cEmployee Dependant\u201d. <\/em><\/strong>
        <\/li>\n<\/ol>\n\n\n\n

        <\/em><\/strong>\n<\/p>\n\n\n\n

        Edit\/Delete Notifications<\/h5>\n\n\n\n

        <\/p>\n\n\n\n

        \n Users can edit or remove an existing notification setup by clicking the three-dot icon in the Actions column and selecting either Edit or Delete, depending on the desired action.\n<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        \"A<\/figure>\n\n\n\n

        Role Based Notifications<\/em><\/h4>\n\n\n\n

        <\/p>\n\n\n\n

        \n The Role-Based Notifications<\/strong> tab within the Department Notifications<\/strong> menu allows system administrators to configure notification preferences based on user roles rather than departments. The page displays a list of system-defined roles such as Admin<\/strong> and Supervisor<\/strong>. Each role can be individually configured to receive specific types of notifications.\n<\/p>\n\n\n\n

        <\/p>\n\n\n\n

        To assign the notifications,<\/strong>\n<\/p>\n\n\n\n

          \n
        1. On Department notifications page, toggle to \u201cRole\u201d based notifications
          <\/li>\n\n\n\n
        2. Check the boxes next to the users you wish to send notifications to.
          <\/li>\n\n\n\n
        3. Click \u201cSave\u201d
          <\/li>\n<\/ol>\n\n\n\n
          \"A<\/figure>\n\n\n\n

          <\/p>\n\n\n\n

          <\/p>\n\n\n\n

          NOTE:<\/em><\/strong>\n<\/p>\n\n\n\n

            \n
          1. You can set only one user for the Absence Request Approver notification. However, for other notifications, user can have multiple notifiers.<\/em><\/strong>
            <\/li>\n\n\n\n
          2. On Bolt, we no longer support notification type \u201cEmployee Dependant\u201d <\/em><\/strong>
            <\/li>\n\n\n\n
          3. Notification Types such as Employee Missing, Daily Exceptions, and Period Ending are displayed based on the settings configured on the main Notifications page. If any of these are set to No there, they will not appear on the Department Notifications page.<\/em><\/strong>
            <\/li>\n<\/ol>\n\n\n\n

            <\/em><\/strong>\n<\/p>\n\n\n\n

            Employee Override<\/em><\/h4>\n\n\n\n

            \n Here, we can perform the employee override. Unlike Legacy, Bolt allows to assign multiple employees at the same time for an override.<\/strong>\n<\/p>\n\n\n\n

            Add Employee override<\/h5>\n\n\n\n

            \n To add employee override, \n<\/p>\n\n\n\n

              \n
            1. Navigate to Department Notifications menu under Admin section of the Express implementation portal
              <\/li>\n\n\n\n
            2. Click on Employee Override<\/strong> tab



              \"A<\/figure><\/li>\n\n\n\n
            3. Click on \u201cAdd Override\u201d will open the side panel

              \"A<\/figure><\/li>\n\n\n\n
            4. Select the employees from the employee selector, user, and notification type

              \"A<\/figure><\/li>\n\n\n\n
            5. Click \u201cConfirm\u201d button. It will show the success toast message and refreshes the grid with newly override records.

              \"A<\/figure><\/li>\n<\/ol>\n\n\n\n
              Edit\/Delete Employee Override<\/h5>\n\n\n\n

              \n User can later edit or delete the employee override by following simple steps:\n<\/p>\n\n\n\n

                \n
              1. Navigate to Department Notifications menu under Admin section of the Express implementation portal
                <\/li>\n\n\n\n
              2. Click on Employee Override<\/strong> tab


                \"A<\/figure>
                <\/li>\n\n\n\n
              3. Click on the 3-dot icon under Actions column for the employee user wants to edit or delete the override


                \"A<\/figure><\/li>\n\n\n\n
              4. Click on Edit or Delete based on the desired action user wants.
                <\/li>\n<\/ol>\n\n\n\n

                NOTE: User cannot assign \u201cAbsence request approver\u201d notification type to multiple users.<\/em><\/strong>\n<\/p>\n","protected":false},"excerpt":{"rendered":"

                The Department Notifications section allows the user to configure and manage notifications at a more granular level, either by Department or Role. This feature ensures that alerts and updates reach the appropriate users based on their departmental affiliation or organizational role, enhancing operational efficiency and targeted communication. Notification Mode Selection…<\/p>\n","protected":false},"author":4,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"ht-kb-category":[282],"ht-kb-tag":[],"class_list":["post-7277","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-express-implementation-portal"],"_links":{"self":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7277","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/comments?post=7277"}],"version-history":[{"count":2,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7277\/revisions"}],"predecessor-version":[{"id":7304,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/7277\/revisions\/7304"}],"wp:attachment":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/media?parent=7277"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-category?post=7277"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-tag?post=7277"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}