Who is this article for?

Administrators and Module Developers and advanced Users configuring and testing notifications.

Administrative access is required.

By default, the weekly email notifications are sent at 10am in the subscriber's default time zone. These settings can be modified on the subscriber level in the Administration Settings under the Global Preferences tab and Daily Notification E-mails section. Adjustments to Email time zone and Time to send (daily) will change the hour that the platform sends daily assignment notification emails. The Day to send (weekly) will change the day on which to send the weekly notification emails for upcoming and overdue assignments.

By default, email notifications are NOT sent from Build/Test/UAT environments for the following reasons:

1. These environments often contain real users with data that is either real data or test data that is like production data. There have been many issues and lessons learned in the past where unintended users get emails from the non-production areas that look like real production data and wind-up with bad information, or worse, wind-up logging in and acting in the non-production area when they think they are in the production area.
2. In addition, a lot of development and testing is going on in the non-production areas which would generate many emails. It’s not necessary or desirable for end users to get these email notifications, since they are just for testing purposes.

To receive email notifications from one or more of these non-production areas, submit a ticket to request/approve access to the email notifications. Please be sure to notify support and submit another ticket  when required emails from these non-production areas are no longer needed.

Requesting Non-Production Email Notifications

When requesting email delivery from a non-production area, describe what results are required. For example, specify if:

1. All users are to get any emails intended for them, in the same manner that they do in PROD. This is only recommended for a Test environment when a small number of designated test users are created. This is not recommended for the UAT environment which contains many real users and real data, so the policy is to never grant delivery of all emails to all users from the UAT environment. This will mean that users in UAT are not able to get password reset emails. When users need to get their passwords reset in UAT, they can contact the customer support administrator and they can reset their password, or alternately, if the customer has setup option 2 below, the customer administrator will receive the password reset email and they can forward it to the end-user that wants to reset their password.
2. One or more users in a subscriber area (i.e., administrators) will receive all emails intended for everyone in the company.

Weekly Overdue/Coming Due Emails

When the overdue/coming due email function is enabled in an environment, an administrator can adjust the Weekly Overdue/Coming Due Emails schedule.

By default, individuals will receive weekly overdue/coming due emails. When a team is assigned to a task all team members receive the initial assignment email and the assignment will always be listed in their Team Assignment dashboard list, however, team members will not receive the Upcoming and Overdue Assignments email.

Administrators can change a company-wide platform Administration Preference setting so Weekly Overdue/Coming Due emails will be sent to all team members and will include upcoming/overdue individual and team assignments.

Once an individual takes ownership of a team assignment the team will be removed from the weekly emails.

Enabling the Overdue/Coming Due Emails

Overdue/coming due emails may not be enabled in your subscriber area. If the Weekly Overdue/Coming Due Email section of the Administrative Preference screen is not visible and you would like additional information on this feature, submit a ticket or contact your account manager.