We are considering 2018 the year of data, privacy, and security, and this second MatrixMaxx release of 2018 — MatrixMaxx 18.2 — overlaps with all of these topics.
Our free Overview Session was on Thursday June 28, 2018, 1pm Eastern time on WebEx. You may see the recording here: https://youtu.be/en7Ew-EZj28
Enhancements available in MatrixMaxx 18.2 include …
- Anonymizer. If a user calls to be ‘forgotten’ and the association determines that this is a legitimate request, any staff member with SiteAdmin access may use the new, red ‘Anonymize Individual Permanently’ button available on the intranet-side from any individual’s profile page. This is not reversible, so please make sure that this is in fact what is desired! This action will replace the user’s name with the word ‘anonymous’ and the user’s number/ID (e.g., ANONYMOUS-FIRSTNAME[4064] ANONYMOUS-LASTNAME[405B00000098] ) and make hundreds of other small changes to eliminate personally identifiable information in the generic product. [Internal reference: Maxx-3209]
- If your organization falls within scope of GDPR, you should contact us to turn this on.
- Turning it on for you will be free of charge, however …
- If your access levels have been customized, it may take a little time to add it to your custom access level(s).
- You also may need to have us add some of your custom fields to the anonymizer, if they contain personally identifiable information, like a resume upload, etc.
- If your organization falls within scope of GDPR, you should contact us to turn this on.
- Personal Information Report. This new report, located in each individual’s ‘Report’ section, provides all critical personal information in one place. The ‘download’ version of this export is currently the same – an HTML page – as there seems to be some indication that HTML is an acceptable format for the ‘download. (This may change as time progresses.) If you see information missing from this report that you believe should be in there, please contact Matrix. [Internal reference: Maxx-3221]
- Exclude from WWW Meeting Roster function (for staff use). If a meeting attendee contacts the association and wishes to not be part of the WWW Roster for a particular meeting, this new function allows staff to do this. This is NOT self-service; an association staff member with access to the attendee’s registration must do this. [Internal reference: Maxx-3223] This can be accomplished by staff through Maxx by either:(1) using the drop-down (yes/no) field on the intranet when inputting a new registration directly into Maxx. This new field is titled: “Exclude from WWW-side Attendee Roster?:” and the help texts reads: “Select this to hide this registration and attendee from the WWW-side attendee roster” … and/or …(2) on existing registrations, staff can use the toggle at the top right of the registration to either exclude from, or include on, the WWW-side attendee roster.
Depending on how this field is managed for each user the attendee will either appear, or not appear, on the WWW rosters.Additionally, this field (yes/no output) is available on registration exports. So you can select this field as an exported field, and then sort the data to remove anyone whose answer is “yes” to the question “exclude from WWW roster”. One example use case for this scenario is that you could (potentially) omit these individuals if you are sharing your roster with paid advertisers, partners, or an outside roster
- New Individual Demographic Checkbox field: Data and Consent Preferences. As the concept of ‘consent’ is still being worked out, especially in regards to the association market, we have added a simple new field to individual demographics on the intranet side for everyone, as a starting point. You may add values to it, and if you want this new field turned on for your WWW Manage Profile form, please contact Matrix Group. There will be a small hourly charge depending on your WWW profile setup. Some of you will not want/need this, but some of you may. [Internal reference: Maxx-3224]
- Help documentation to support specific articles of GDPR. The MatrixMaxx team has walked over some of the key facets of GDPR and prepared this GDPR help article to assist association staff in answers questions and requests.
- Other changes/upgrades/fixes of note:
- Fixed Bug: Events Section of Meeting Registration Page Not Displaying Registrant Name on $0 Events [internal reference 116213]
- Individual Application Export and Advanced Individual Search Export Missing Shipping Addresses for Individuals [internal reference 116398]
- Tweaks to social media pulls from Scrape and Drape pages [internal reference 116097 ]
- IMPORTANT: Some older elements may be cached in your browser. If a page is not formatting properly, or elements are missing or not behaving properly, please do a ‘hard refresh’ on the page prior to contacting Matrix to report an issue. (Using a keyboard, a browser can be forced to pull all elements of a page, again, by holding down the SHIFT key and clicking the browser refresh button.)
Security, Privacy and Integrations
In addition to the code upgrades released in MatrixMaxx 18.2, there have been other efforts going on in 2018. These efforts have including security upgrades, privacy considerations, and fresh integrations.
- Upgrading all Communications to be in the secure TLS 1.2 protocol, as part of the new PCI regulations. There was an announcement about this back in January, and we are now down to a handful of clients with legacy applications that need upgrading. We have already reached out to several clients, and the Matrix Services team is reaching out to more.
- Forcing all WWW websites to serve in full HTTPs secure. While this concept has its roots in PCI, its expansion to the full site has been driven by the major browsers upgrading to show obvious non-secure icons and the major search engines down-grading non-secure sites. This is an overlap with the Matrix Services division, and their goal is to have all sites in full HTTPs by the end of the year, if not sooner.
- Encrypting all passwords to full 1-way ‘hash’ encryption, as part of the new PCI regulations and current industry standard. MatrixMaxx started out, as most systems did, with plain text passwords that could be ‘recovered’ by users. However, we have shifted to encrypted passwords with resets, and have slowly been working with legacy implementation to upgrade them. Now, the new PCI regulations are dictating that it is time to finish this up. If your database still has plain text passwords and you haven’t heard from Matrix yet, you will soon.
- Upgrades of key operating software. From Ubutu14 to Ubuntu18, and from Apache to NGINX. One client is already operating on this new stack; our goal is for all clients to be on this by the end of 2018.
- Integration between MatrixMaxx and the Sharpspring marketing automation platform is underway. Stay tuned for more info on this later in the summer or fall.
Our free Overview Session was on Thursday June 28, 2018, 1pm Eastern time on WebEx. You may see the recording here: https://youtu.be/en7Ew-EZj28