{"id":708,"date":"2018-11-20T22:23:41","date_gmt":"2018-11-20T22:23:41","guid":{"rendered":"\/agile\/?post_type=ht_kb&p=708"},"modified":"2024-08-08T20:50:34","modified_gmt":"2024-08-08T20:50:34","slug":"department-notifications-screen-legacy","status":"publish","type":"ht_kb","link":"\/agile\/knowledge-base\/department-notifications-screen-legacy\/","title":{"rendered":"Department Notifications – Screen – legacy"},"content":{"rendered":"
\n

The Department Notifications screen is used to control which supervisor or admin user, will receive notifications fromm ESS employees.<\/p>\n

 <\/p>\n

NOTE: For express or portal users, a newer methodology has been devised that is role based and therefore this screen might not apply.<\/p>\n<\/div>\n

\"\"<\/p>\n

What are notifications<\/h5>\n

Notifications are used by employees with access to the Employee Self Service (ESS) module, to notify their supervisor of an action they have taken. For example they can notify their supervisor that their contact information has changed, or that their Weekly Timesheet has been submitted for approval. The most common notification is an absence request. In this screen you can decide who your employee\u2019s notifications will go to.<\/p>\n

Choosing who will receive a notification<\/h5>\n

Notifications are configured by department. Simply select the department you want, then add the notification user for the type of notification desired. If a department has no supervisor assigned, any notifications from employees of that department, will go to the department supervisor on the next level of the department tree.<\/p>\n

For example, if \u201cOffice\u201d, a sub-department of \u201cToronto\u201d, has no absence request approver, but the \u201cToronto\u201d department itself has an approver (Sarah), all absence requests from those Office employees will go to Sarah. \u201cProduction\u201d, also a sub-department of \u201cToronto\u201d has its own absence request approver defined at that level, Frank. Therefore those requests will go to Frank, and not to Sarah.<\/p>\n

 <\/p>\n

 <\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

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

Types of Notifications<\/h5>\n

Employee Private \u2013 the employee has changed their address or contact information<\/i><\/p>\n

Employee Dependent \u2013 the employee has changed their family details<\/i><\/p>\n

Timesheet Notification \u2013 the employee has submitted their Weekly Timesheet for supervisor approval<\/i><\/p>\n

Absence Notification \u2013 the employee has submitted an absence request (notification only)<\/i><\/p>\n

Absence Request Approver \u2013 the employee has submitted an absence request (approval\/rejection)<\/i><\/p>\n

Scheduling Availability \u2013 the employee has changed their scheduling availability preferences<\/i><\/p>\n

For newer notifications like publish schedule, schedule change notifications, pay period notification, daily exception notice and missing employee\u00a0 refer to the 11.6 release notes.<\/p>\n

https:\/\/help.synerion.com\/agile\/article-categories\/11-6\/<\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

The Department Notifications screen is used to control which supervisor or admin user, will receive notifications fromm ESS employees.   NOTE: For express or portal users, a newer methodology has been devised that is role based and therefore this screen might not apply. What are notifications Notifications are used by…<\/p>\n","protected":false},"author":3,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"ht-kb-category":[39],"ht-kb-tag":[],"class_list":["post-708","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-general-topics"],"_links":{"self":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/708","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\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/comments?post=708"}],"version-history":[{"count":2,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/708\/revisions"}],"predecessor-version":[{"id":711,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb\/708\/revisions\/711"}],"wp:attachment":[{"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/media?parent=708"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-category?post=708"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/help.synerion.com\/agile\/wp-json\/wp\/v2\/ht-kb-tag?post=708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}