GDPR: opt-in/opt-out for multiple topics

I’m currently testing out the new opt-in / opt-out functionality with SuiteCRM 7.10.x. Don’t quite get it yet. But what seems clear is that it only affects email addresses globally through-out the entire SuiteCRM instance.

For our use we’d need some way to have a customer choose which topics to sign up to or not. How could this be done?

The way I imagine it working is a smart-link that is included in every campaign email. The smart-link is specific to the recipient.
Upon receipt of the email the recipient can click on the smart-link and see a list of possible topics and which one he/she’s subscribed to. The user can change and save these topic-subscriptions. This would affect the target lists the user is included in (topic-specific suppression lists).

The user can also opt-out of all emails from our company, which would lead to a SuiteCRM-global opt-out for this email address.

Any ideas? Is there any plugin out there that makes this easier?

It seems to me you just need to manage several different Target Lists.

The “opt-out” concept is more of a privacy thing, it’s not a setting. So it has more drastic, system-wide effects (by design).

You can use Tracker URLs in Campaigns to let people click to be included in a Target List. Try playing with these option to see if they are enough for your needs.

Also, you might want to check out the AOP Portal, because if you need to develop a special screen for your users to interact with their own records in SuiteCRM, with personal areas and personal passwords, then that is a start.

Thanks. I’m aware of all this current functionality. having user/login makes no sense in our case just to change newsletter/topic subscription settings.

I’m not sure you understand that with GDPR users need to opt-in to every single use case (i.e. newsletter topic) seperately. So I’m looking for a feasible way to do this with SuiteCRM. Merely “managing” Target-Lists is not GDPR-ready, unless all target lists belong to the same topic/business field that the recipient has given recorded consent for.

Please open an Issue on GitHub if you think there are parts of GDPR that are still not taken care of.

GDPR is a big beast and it’s hard to know exactly what people require, so user contributions are very welcome.