Like many others I'm sure, we're using COVID downtime as an opportunity to tackle our communications tracking and make the migration to Contact Permissions ahead of v16. My specific question for the community, though, is...
I see that there's a setting in T_DEFAULTS that can control whether permissions can be set at the household level, or for individuals only (which is the GDPR requirement). Looking in the crystal ball of future data legislation that might take shape here in N. America, I'm trying to make the most informed decision now to serve us well in the future. The CCPA is the closest equivalent to the GDPR in the U.S. that I'm aware of, and some cursory Googling suggests that it's not as restrictive as GDPR in this particular area and allows people to be aggregated together as a household for purposes of data management.
Choosing to set up and migrate permissions to individuals would add a lot of clarity and granular control, and if it's something we may need to approach in 5-10 years anyway I'd rather get the jump on it instead of kicking the can down the road. It'd be a big transition and changing of old habits though, as much of our contact data presently is associated with households and people are used to that setup (myself included). I suppose you'd also need to revsiit your usual extraction criteria if tickets and contributions are still being booked to households (a whole lot of checking that 'Search Household' box!) and also figuring out how to navigate when one member of a household opts out of a contact type while another member is still opted in.
Has anyone grappled with this question and come down on either side, or want to explore it together? Also, if you've migrated to Permissions already or are doing so now, and have success or horror stories, feel free to reach out - I don't want to derail this thread from the main question, but would love to chat about this more broadly!
Hi Evan, We have recently migrated to contact permissions and did move to individuals. Feel free to contact me at stevens@midlandcenter.org.
Hi Terry,
Did you have a lot of legacy household contact information (email addresses, logins) that you had to migrate?
Thanks Terry! I'll drop you an email. Gawain, would you be interested in being part of the conversation as well?
Sure, thanks!
Gawain we had Tessitura write a script to move our legacy Household and Individual restrictions to contact permissions individual accounts. We moved anything marked on the household to each of the individuals within the household unless an individual on the household had something different. For those individuals who had their own restrictions their contact permission were updated to match. All this was completed with a script. Regarding emails that is a lot more difficult. We did not move email addresses from households to individuals because it is impossible to know who they should belong to. We did take some steps to help facilitate the move from household emails to individual emails, most of this is being done manually while serving our customers on the phone. Our hopes are within time, or by the time GDPR comes our way we will have most of our constituent email's under the individual accounts. We have set a six month date on contact permissions so customers are asked regularly to update them. We also are using the TNEW contact permission plug in to catch online orders and have them update as well. We can set up a time to talk with Evan so I can pass on a bit more detail.
Ok sound good