---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Create email notifications for translation request due dates

# Create email notifications for translation request due dates {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
As an admin, you can create email notifications triggered by translation request due dates.

## Before you begin

Create your own notification category to identify and group your notifications related to Localization Workspace translation projects. For instructions see [Create notification categories](https://servicenow-prod.fluidtopics.net/DASk94Dmhx2~I72XCdR17w "You can create notification categories to identify and group related notifications that are listed in the notification settings for your users.").

Role required: admin

## About this task

From version 2.0.2, your users may set a due date when requesting translations in Localization Workspace. You can reference these due dates to send email notifications.

For more information see [Request translations in Localization Workspace: Estimate and Due Date](https://servicenow-prod.fluidtopics.net/7_1BSHDxyq7Vi5yrn17DXg "As the final step in creating a translation request, you can review an informational cost estimate and optionally set a due date. The due date can be used to trigger email notifications."). For background information about configuring email notifications, see [Create an email notification](https://servicenow-prod.fluidtopics.net/vaPuVLOcN_zPS8jyrTPDmw "Create an email notification specifying when to send it, who receives it, what it contains, and if it can be delivered in an email digest.").

The following procedure is specific to notifications for Localization Workspace translation request due dates. In the example scenario, a notification is sent when a translation request is past due (the request is still in progress after its due date).

## Procedure

1. Navigate to AllSystem NotificationEmailNotifications.
2. Select New.
3. Fill in the fields according to the following guidance.

   | Field | Description |
   | Name | Enter a unique, descriptive name for these notifications. |
   | Table | Select the Localization Project \[sn_lf_project\] table from the list of tables. |
   | Category | If you have already set up your own category for these notifications, you can select it from the drop-down list. For information see [Create notification categories](https://servicenow-prod.fluidtopics.net/DASk94Dmhx2~I72XCdR17w "You can create notification categories to identify and group related notifications that are listed in the notification settings for your users."). |
   |-|-|

   {#lw-email-notif-due-dates__choicetable_gpm_cth_nhc}  
4. On the When to send tab, fill in the fields.

   | Field | Description |
   | Send when | Select <kbd class="ph userinput">Record inserted or updated</kbd>. |
   | Updated | Select this check box. |
   | Inserted | Clear this check box. |
   | Conditions | In the example, two conditions are set: 1. <kbd class="ph userinput">State is In Progress</kbd> 2. <kbd class="ph userinput">Due date before Today</kbd> {#lw-email-notif-due-dates__ol_ugt_ky4_nhc} |
   |-|-|

   {#lw-email-notif-due-dates__choicetable_fpy_zx4_nhc}  
5. On the Who will receive tab, fill in the fields according to your organizational requirements.

   | Field | Description |
   | Users | Select the lock icon ![]() to add an individual user from the User \[sys_user\] table. |
   | Users/Groups in Fields | Select the lock icon to add recipients from fields in the Localization Project \[sn_lf_project\] table. |
   | Groups | Select the lock icon to add a group of users, such as Localization Requestor, from the Group \[sys_user_group\] table. |
   | Subscribable | Option to enable all users to subscribe to the notification. Note: Recipients can receive email about records that they can't normally access from the user interface, so consider the sensitivity of the information before selecting this option. |
   |-|-|

   {#lw-email-notif-due-dates__choicetable_kyt_4th_nhc}
6. On the What it will contain tab, fill in the fields according to your organizational requirements.

   | Field | Description |
   | Email template | You can search for an existing template. |
   | Subject | You can use variables from the Localization Project \[sn_lf_project\] table, available under Select variables. |
   | Message HTML | You can use variables from the Localization Project \[sn_lf_project\] table, available under Select variables. Example variables from this table: * `${short_description}` for Short Description * `${due_date}` for due date * `${made_sla}` for Made SLA {#lw-email-notif-due-dates__ul_fqy_y1p_nhc} |
   |-|-|

   {#lw-email-notif-due-dates__choicetable_bxw_f1p_nhc}
7. Select Submit (or Update if you are editing) to finish the record.

## What to do next

After creating or updating a notification, review its record in the Notifications \[sysevent_email_action\] table. You can select Preview Notification to open an example of the email notification. Use
this function to confirm how the notification appears to recipients.

For more information, see [Preview email notifications](https://servicenow-prod.fluidtopics.net/XRREENdb2z~U_6HmYdQH3g "You can preview what notifications look like before you actually enable the instance to send them.").

*[\>]: and then