[Meta] Ability for managers and applicants to turn on/off different kinds of notifications, choose which channel they receive notifications, and manually adapt text of notifications

[frjo]

As a I want to Hypha to send me notifications when important statuses are triggered so that I can do the right thing.

Minimum Viable Product

Right now, we're waiting for some feedback from others on what types of notifications are needed and what they should apply to, so we'll start with this notification:

• 5 days before the current round closes and if no new round exists, Hypha sends an email with a message.

Message subject:

Current round closes in 5 days. No new round exists.

Message body:

Dear $NAME,

$FUNDNAME $ROUNDNAME is currently open and will close in 5 days. No new round exists. You should create the next round."

When the user clicks on the "create the next round" link, it brings them to the page in Wagtail to create the new round.

[ei8fdb]

These notifications are part of a bigger product design question: what notifications does the user need from Hypha?

Here are some ideas, some possibilities of how these might work. @danblah, @fourthletter and others, I'd appreciate your comments here.

Design questions

Who receives these notifications?

• The round leader?
• The fund owner?
• Team admin
• Applicants (in the case of flash grants)
• Someone else?

What should these notifications apply to?

Some possibilities:

• Funds
• Rounds
• What else?

What notifications are needed?

Here are some possibilities that might be useful.

Notifications Funds:

1. The current round is due to close soon.
2. The current round is closing soon and no new round exists. (This one is the first that @danblah requested)
3. The next round is due to open soon.
4. Others?

Notification message design

Should these notifications suggest/require user action or should they just notify?

My view is the first; these notifications need to provide the user with information about 1) the current status, 2) and what will happen next, 3) if they need to take action, and 4) what action is required.

e.g. an example notification message could be:

"Fund A July round is open and will close in X days. No new round exists. You should create the next number of rounds."

[fourthletter]

Here is a document to highlight communication and notification challenges. It's a start, but will mostly likely require a deeper dive.

[fourthletter]

related to #2225

[ei8fdb]

Hypha notifications

[fourthletter]

Here is a compilation of email & slack communication/notifications to applicants and staff: https://docs.google.com/document/d/1Y2oZWvrysBO9OjuoPbviI-UruUnib9P6TkBWHgam_Is/edit#

Here is matrix to show who receives notifications & what notifications are needed https://docs.google.com/spreadsheets/d/1afjsbYjEpfwxXGblghAVf--xONZOJn7JlcSVtXy2z7k/edit#gid=0

Summary
Who receives these notifications?

• Applicants receive approximately 5 automated emails related to workflow status change
• Applicants also receive bespoke communication within Hypha. They are notified with an email letting them know that a message is waiting for them within Hypha.
• 'Lead' receives notifications via slack regarding all adjustments related to the fund/round
• Reviewer receives notification when a review has been submitted, and the reviewer can no submit their review
• AC (external reviewer) do NOT receive automated emails.

What notifications are needed?

• Staff receive notifications when a new application has been submitted,

Notifications Funds:
The current round is due to close soon.
The current round is closing soon and no new round exists. (This one is the first that @danblah requested)
The next round is due to open soon.
Others?

[fourthletter]

related to #2704

[fourthletter]

closing because of epic #2812