Page Comparison

...

	Event	Need user action?	Can turn off?	Sent from	Include user message?	Include unsub link?	Include user profile setting link?
1	Someone invited me to a team	Yes		Synapse Notification	Yes	Yes	No
2	Someone accepted my invitation	No		Synapse Notification	No	Yes	No
3	Someone requested to join my team	Yes		Synapse Notification	Yes	Yes	No
4	Someone granted my request	No		Synapse Notification	No	Yes	No
5	Someone submitted a submission for my team	No		Synapse Notification	No	Yes	No
6	Someone requested to view my entity	Yes		SWC	No	No	Yes
7	Someone shared an entity with me	No		SWC	No	No	Yes
8	Someone sent me a message	No		Any client & email	Yes	No	Yes
9	I created a verification submission			Synapse Notification	No	Yes	No
10	My verification submission status has changed	No		Synapse Notification	Yes	Yes	No
11	A new thread has been created	No	Yes	Broadcast Message Worker	No	No	No
12	A new reply has been created	No	Yes	Broadcast Message Worker	No	No	No
13	Password Reset	No	No		No	No	No
14	Welcome to Synapse	No	No		No	No	No
15	Delivery Failure	No	No		No	No	No
16	Additional Email Validation	No	No		No	No	No
17	New Account Email Validation	No	No		No	No	No
18	After a new submission is created	Yes	No	Synapse NotificationYes	Broadcast Message Worker	No	No	No
19	After a submission is approved	No	NoSynapse Notification	Broadcast Message Worker	No	No	YesNo
20	After a submission is rejected	Yes	NoSynapse Notification	Broadcast Message Worker	Yes	No	YesNo

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

Jira Legacy

server	JIRA (sagebionetworks.jira.com)
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	ba6fb084-9827-3160-8067-8ac7470f78b2
key	PLFM-2578

user asked that we have the same behavior when the ACL is changed from different clients. Also,

Jira Legacy

server	JIRA (sagebionetworks.jira.com)
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	ba6fb084-9827-3160-8067-8ac7470f78b2
key	SWC-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:

...

Versions Compared