Platform
GDPR
We continued our work on GDPR. Here's what's new:
- Org admins can update email and offline opt-in behavior from the Email Opt-In tab in the organization settings.†
- Org admins have more control over the services integrated into their platform. In particular, we allow organizations to remove their Akismet, Mailgun, and Segment integrations. More information about our authorized subprocessors (which do not include Akismet, Mailgun, or Segment) are here: https://controlshiftlabs.zendesk.com/hc/en-us/articles/360000175976-ControlShift-Authorized-Subprocessors.†
- Radio buttons were misaligned on some organizations' petition signature pages. This should be fixed.
- We're now providing more information about a user's data processing consent history, including the dates of all data processing consents, data consent type external IDs, and whether the consent was implicit or explicit.†
- Org admins can now disable delivery PDFs for all petitions on the platform. (It was already possible to disable the delivery CSV.) This option is available from Configure > Settings > Options > Petitions.†
- Org admins can now enable their platform's cookies consent banner (from Configure > Settings > Options > Disclaimers). From there, you can also customize the text used in the banner.†
- We've updated the "must be accepted" error message that's shown when someone does not consent to data processing. This error message is now red and looks like other signature form errors.
- The member activity JSON (which is available to members will full accounts and org admins) now includes data processing consent history.
- For organizations with many translations, the email opt-in page took a bit to load. We're now disabling the Save button during page load to make it more clear if the page is still loading.
- It is now possible to delete individual petition signatures via API. More information is available: https://developers.controlshiftlabs.com/#signatures.
- Organizations can now set their Country field from the Time Zone and Locale tab of the settings page. For organizations based in Europe but operating in multiple countries, setting this option will mean that we send users down the GDPR path (collecting data processing consent, etc.) even if the user is based in a country that doesn't require GDPR-compliant consent (like the US).
New
- As part of our admin redesign work, we've updated the organization Settings page and moved some things around. The biggest changes are:
- The Settings link is at the bottom of the left-hand sidebar, under the new Configure heading.†
- The Integrations tab now includes more CRM configuration options.†
- The CRM Sync page is now in the Integrations tab of the Settings page.
- The Categories page is now a tab in Settings.
- The Content tab (previously CMS > Content) is now a tab in Settings.
- Promoted Petitions (which cover petitions promoted on the homepage and on the daisy chain) are now included in a tab in Settings.
- The Stories page (previously CMS > Stories) is now a tab in Settings.
- Organization's Optimizely settings have moved from the Options tab to the Integrations tab.
Updates / Bug Fixes
- Infrastructure improvements.
- We fixed a bug that prevented the sending of campaign admin invitations from an instance's secondary domain.
- Users signing petitions, creating accounts, or RSVPing using a yahoo.com.ar were asked if they meant to use yahoo.com.au. We now recognize .ar as a valid top-level domain.
Petitions
Updates / Bug Fixes
- Some organization-level custom fields were not rendering appropriately on signature PDFs. We think we've fixed this issue, but if you see any outstanding issues with the delivery PDF, let us know.
- We fixed a bug that caused one-click signatures to not work for organizations using ActionKit.
- The bulk signature upload tool didn't work well with EU data processing consent restrictions. Now, any users who are uploaded by admins will be given the current data processing consent version.†
- On a petition's Email Supporters page, the Details section (under To) sometimes showed an erroneous total signature count. This should be fixed.
- We fixed a bug that caused keyword searches to sometimes fail on an Effort/Landing Page's landing page.
Events
New
- Event forums are back! Attendees, hosts, and admins can once again communicate within the forum on an event page. Importantly, attendees are also able to unsubscribe from forum updates.†
- Admins can now choose to enable/disable event forums at the organization, calendar, or individual event levels.†
- Events now support custom fields. This can be useful for collecting event-specific information like dietary restrictions, t-shirt size, etc. The custom fields can be either text fields or checkboxes.†
- Event hosts can now mark attendees as confirmed or attended. On the attendees tab, hosts will see a drop down allowing them to choose from various statuses: attending, not attending, confirmed, and attended. This may be useful if your organization wants hosts to check users into an event.†
Updates / Bug Fixes
- For events with waitlists, when attendee's user accounts were deleted, people would receive an email informing them that they'd been promoted from the waitlist even if the event had passed. We've updated the code so that email is not sent for past or hidden events.
- We made a small update to the event creation form's UI – the attendee limit help text is now next to, not beneath, the attendee limit field.
Groups
Updates / Bug Fixes
- We've fixed a bug where: when creating an account as part of the new group creation process, the user would see a 404 page.
- We've added some whitespace under the admin tools banner because the banner was overlapping page elements for some organizations.
TakeCharge
Updates / Bug Fixes
- We've ended our support of TakeCharge, and it is no longer available. For organizations wishing to start/continue collecting donations in TakeCharge, please see: https://controlshiftlabs.zendesk.com/hc/en-us/sections/360000010936-Donations-in-ControlShift.
VisitThem
Updates / Bug Fixes
- Infrastructure improvements.
- In the "Found an error or missing data?" section of the search results page we used to say "Send us an email", now we say "Contact tech support".
† This feature required new text strings. If you're using the platform in a language other than English, you may need to provide updated translations. (Note that this will include publicly visible and admin-only text.)
Oddest bug fix, based solely on commit title: "Google Maps has become unsure of what zipcode 100 madison avenue is in."
Comments
0 comments
Please sign in to leave a comment.