Skip to main content

How to setup notification preferences for CUSIP maturity emails

Step-by-step walkthrough of how to define which users should receive notification emails for CUSIP maturities

Important Note: Only users with an Admin role can edit this setup.

Overview

When a Treasury Bill is approaching maturity, the platform automatically sends an email 7 days before maturity. The email provides a deadline for instructing the platform to withdraw the funds or change the investment term before the T-bill is automatically rolled over.

Notification Preferences allows customer administrators to control who receives email notifications for upcoming maturity events.

Administrators can configure recipients in two ways:

  • By user role: Notify everyone who currently has, or is later assigned, a selected role.

  • By individual user: Notify specific users regardless of their role.

You can use either method independently or combine both. Notification preferences are configured by customer administrators.

Access the configuration function

To open the configuration screen, click your user icon and choose Notification preferences from the menu:

Configure recipients

By default, “Administrator” role is selected: all active users with the Administrator role receive CUSIP maturity notifications. The screen below accordingly displays “Administrator” in column “Recipients” with the count of currently active users with that role.

Configure recipients by role

Selecting a role automatically subscribes all current and future members of that role to the notification.

To add a role:

  1. Go to “Notification Preferences”.

  2. Click “Edit”.

  3. In “Add roles as recipients”, find the role(s) you want to subscribe.

  4. Click “Add role”.

  5. The role is added as a recipient and the number of members currently assigned to that role is displayed.

In the example below, roles “Administrator” and “Checker” are selected as email recipients

Important Note: A role subscription also applies to users who are assigned that role in the future. You do not need to update notification preferences when a new user is added to the role.

To remove a role:

  1. Find the selected role in “Add roles as recipients”.

  2. Click “Remove”.

  3. All users receiving the notification through that role will no longer receive it unless they are also explicitly selected as individual recipients.

Configure recipients by individual user

You can also subscribe individual users without subscribing their entire role. Individual recipients are useful when, for example, only one member of a team needs to monitor upcoming T-bill maturities.

To add an individual user:

  1. In section “Not receiving this notification”, click “Add”: the selected user is moved to section “Receiving this notification”. Note: section “Not receiving this notification” excludes the users already selected through their role.

To remove an individual user:

  1. Click “Remove” in section “Receiving this notification” to stop that individual from receiving the notification.

Understanding the recipient list

The page separates users into two sections:

  • “Receiving this notification”: This section shows everyone who will receive the notification under the current configuration. Each user indicates how they are subscribed:

    • Via role: The user receives the notification because one of their roles is subscribed.

    • Individual recipient: The user was specifically selected to receive the notification.

    • The number displayed in the section header is the total number of users currently receiving the notification.

  • “Not receiving this notification”: This section shows active users who are not currently subscribed.

In the example below, role “Checker” and 2 individual users are selected as email recipients

Key points to remember

  • The notification is sent 7 days before each T-bill maturity.

  • Recipients can be configured by role, by individual user, or both.

  • Role-based subscriptions include current and future members of the role.

  • A user can receive the notification because of a role and/or an individual subscription.

  • A user receiving the notification via a role cannot be removed individually; the role subscription must be removed.

  • The recipient lists provide a clear view of who will and will not receive the notification before the configuration is saved.

Did this answer your question?