2. Notifications
2.1 How you are notified
| Channel | What it is | How it is set up |
|---|---|---|
| In-app bell | A bell in the top bar with an unread badge (a red count of unread items). The badge is hidden at zero. | Always on |
| Notifications page | The full list, at /notifications | Always on |
| A message to your work email | Set up by the system administrators | |
| Browser push | An alert on your device | You turn it on for each device |
Every message has a severity: INFO, ACTION, WARNING or CRITICAL.
Delivery happens straight after the event. A retry job at 02:00 UTC tries again anything that failed. SMS is not used for notifications yet.
2.2 Who is told about which event
You only receive a message when you hold the right role and the record is in your scope. Read-only investor users never receive operational alerts.
| Event | Who is told |
|---|---|
| A marketplace request is submitted | The Platform Super Administrator. The applicant gets "Request received". |
| A finance application decision is needed | Finance Approvers and State Coordinators |
| An application is waiting in a review stage | Programme Administrators, State Coordinators, Institution Administrators and Finance Entry Officers |
| A financing case needs action | Programme Administrators, Institution Administrators, Finance Entry Officers and Finance Approvers |
| A payment waits for checking | Finance Approvers |
| A payment is prepared | Programme Administrators, Institution Administrators and Finance Entry Officers |
| A monitoring warning is raised | Programme Administrators, State Coordinators, Monitoring Analysts, Institution Administrators and Finance Approvers. For CRITICAL case warnings, the case team too. |
| A scheme member applies or registers | Registrars (Client System Administrator, Programme Administrator, State Coordinator) |
| A scheme redemption is requested | Scheme administrators (Client System Administrator, Programme Administrator) |
| A staff invitation is accepted | The invitee and the person who sent the invitation |
| The security policy is changed | The Platform Super Administrator who made the change |
| A staff message is sent | The people chosen: one person, selected people, a whole role, or all active staff |
2.3 The notifications page
Who can use it: every staff member.
Steps
- Click the bell in the top bar, or open Notifications in the menu.
- Read the three counters at the top: Unread, All activity and Email and push deliveries.
- Find the message in the table. The columns are Notification, Message, Channel, Status and Created.
- Click Open record to go to the record the message is about.
- Click Mark as read on one row when you have finished with it.
- Click Mark all read at the top of the page to clear every unread message at once.
What happens next
- The unread badge goes down.
- Messages stay in All activity. Nothing is deleted.
- The Email and push deliveries counter shows that a message really went out. Use it when someone says they never got a message.
Common problems
- The badge is different from the list. Refresh the page. The badge counts unread items only.
- I did not get an email. Check Email and push deliveries. If the status shows a failure, tell the Client System Administrator. The retry job tries again each night.
- I cannot see a message about a record I can open. The message may go to a role you do not hold. Ask the Client System Administrator which roles receive that event.
2.4 Turn on browser alerts for a device
Who can do it: every staff member, for their own device.
Steps
- Open Notifications.
- Click Enable alerts in the push control.
- Allow notifications when the browser asks.
- To stop alerts on this device, click Turn off.
What happens next: alerts arrive on that device while the browser is running. Each device has its own switch.
Common problems
- There is no Enable alerts button. Your browser may block notifications. Check the site settings in your browser.
- Alerts stopped. Turn alerts off and on again on that device.