Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


EventNeed user action?Can turn off?Sent fromInclude user message?Include unsub link?Include user profile setting link?
1Someone invited me to a teamYes
Synapse NotificationYesYesNo
2Someone accepted my invitationNo
Synapse NotificationNoYesNo
3Someone requested to join my teamYes
Synapse NotificationYesYesNo
4Someone granted my requestNo
Synapse NotificationNoYesNo
5Someone submitted a submission for my teamNo
Synapse NotificationNoYesNo
6Someone requested to view my entityYes
SWCNoNoYes
7Someone shared an entity with meNo
SWCNoNoYes
8Someone sent me a messageNo
Any client & emailYesNoYes
9I created a verification submission

Synapse NotificationNoYesNo
10My verification submission status has changedNo
Synapse NotificationYesYesNo
11A new thread has been createdNoYesBroadcast Message WorkerNoNoNo
12A new reply has been createdNoYesBroadcast Message WorkerNoNoNo
13

Password Reset

NoNo
NoNoNo
14Welcome to SynapseNoNo
NoNoNo
15Delivery FailureNoNo
NoNoNo
16

Additional Email Validation

NoNo
NoNoNo
17

New Account Email Validation

NoNo
NoNoNo
18After a new submission is createdYesYesBroadcast Message Worker
NoNoNo
19After a submission is approvedNoNoBroadcast Message Worker
NoNoNo
20After a submission is rejectedYesNoBroadcast Message Worker
YesNoNo


From this list, 6 and 7 should be sent from Synapse Notification instead of sending from SWC. In fact, in 

Jira Legacy
serverJIRA (sagebionetworks.jira.com)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdba6fb084-9827-3160-8067-8ac7470f78b2
keyPLFM-40792578
 user asked that we have the same behavior when the ACL is changed from different clients. Also, 
Jira Legacy
serverJIRA (sagebionetworks.jira.com)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdba6fb084-9827-3160-8067-8ac7470f78b2
keySWC-3545
 could be solved by adding an API for requesting access. Email should be send from the backend as a Synapse Notification email.

Users requested that after the immediate fix, we would also provide the following:

  • When a user goes to unsubscribe from Synapse, we would provide them with more fine grant control. So that a user could choose to unsubscribe from certain topics in Synapse. 
    Jira Legacy
    serverJIRA (sagebionetworks.jira.com)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdba6fb084-9827-3160-8067-8ac7470f78b2
    keySWC-3310
  • Provide a way for the user to retrieve all unread message while they are unsubscribed from Synapse
    Jira Legacy
    serverJIRA (sagebionetworks.jira.com)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdba6fb084-9827-3160-8067-8ac7470f78b2
    keySWC-3311