I would suggest a slight rephrasing as simply "Stop receiving emails like this"; I don't think we need to include the template name here.

@dannykopping I would like to take a look at this

@joobisb go for it 👍 let me know if you run into any issues. Thanks!

hi @dannykopping

I believe we cannot make direct API calls from the received email to our backend server due to CORS and other issues, so I was thinking of the following:

• Instead of making an API call, add a query parameter to the "Manage Notifications" link. When the user lands on the notifications page, check for this parameter and perform the unsubscribe action.

• In the frontend code, check for the unsubscribe parameter, perform the action (PUT api/v2/users/{user}/notifications/preferences API), and display the same Notification preferences updated toast.

wdyt ?

Sounds good to me @joobisb!

Hi @BrunoQuaresma,

#14520 (comment) continuing this conversation here as I'm unable comment further on the PR

Thank you for reviewing the PR and merging it.

I appreciate you fixing the Notification stories as well, didn't know we could use decorators to spy the API before the story is rendered

had one question though, this message was added to show the user which template was disabled, wasn't it needed?

displaySuccess(`${template.name} notification has been disabled`);

@joobisb In order to obtain the template name, we would have to wait for the templates to be fetched, which would block the update request until that process was completed. In my opinion, having the name doesn't provide significant value as it slows down the action. Additionally, since the other toast messages don't include the template name, I think it would be acceptable to omit it. If we believe that including the name in the notification is essential, then we may need to update the API or possibly the email link to provide the name without blocking the delete action. Makes sense?

@joobisb In order to obtain the template name, we would have to wait for the templates to be fetched, which would block the update request until that process was completed. In my opinion, having the name doesn't provide significant value as it slows down the action. Additionally, since the other toast messages don't include the template name, I think it would be acceptable to omit it. If we believe that including the name in the notification is essential, then we may need to update the API or possibly the email link to provide the name without blocking the delete action. Makes sense?

@BrunoQuaresma it does. thanks for clarifying!