Add another checkbox to email preferences

[chrifro]

Jakob suggested adding another checkbox for the onboarding flow emails to the notification preferences. Previously we thought to keep the unsubscribe logic of the onboarding emails at customer.io to keep the effort of the new changes as low as possible. We now reconsidered that and decided to implement another checkbox, as the implementation isn't that complex and because there are several benefits coming with it:

• it can be confusing if a user unsubscribes to all emails in the dashboard but still receives onboarding emails
• the behavior of the unsubscribe link in emails isn't consistent (sometimes it refers to customer.io and other times to the dashboard)
• it's a nicer way of handling data, all information would be stored in the same place

Could you add another option as suggested in the mock below @laushinka ? :) It closely relates to #4793
The checkbox should be enabled for all users. Enabling this checkbox should not have any consequences for the user. They will only receive the onboarding emails right after user creation.

cc @jakobhero

[csweichel]

@svenefftinge Please decide how important this is w.r.t. to the other issues and schedule/remove accordingly.

[svenefftinge]

We have many more important things scheduled. I wonder how much effort this is. If it's a matter of two hours of work it might make sense to just do it. @laushinka ?

[laushinka]

@svenefftinge It shouldn't take much effort assuming the behavior is exactly like the other checkboxes. I'll take this on then.

Just one question for @ChristinFrohne, what does "Enabling this checkbox should not have any consequences for the user" mean?

[chrifro]

great thanks @laushinka

what does "Enabling this checkbox should not have any consequences for the user" mean?

I just meant to give some context to the impact of the checkbox. There is no action required for that from your side. I'll make sure that the onboarding emails are the only ones that this segment will receive.

[laushinka]

There is no action required for that from your side. I'll make sure that the onboarding emails are the only ones that this segment will receive.

I will still need to make sure tracking events get sent, right? @ChristinFrohne @jakobhero

[laushinka]

/schedule

[roboquat]

@laushinka: Cannot schedule issue - issue does not belong to a team. Use /team to specify one.

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[laushinka]

/schedule

[roboquat]

@laushinka: Issue scheduled in the meta team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.