Platform

New

• We've added a new Google Sign-In integration, which is available from the org admin homepage > Settings > Integrations tab. This integration will allow your members to sign in with one click using their Google accounts. †
  
  
  
• In addition to Google Sign-in, we've also made a bunch of other updates to the new account creation and log in pages. These updates include:
  • • By default, we're no longer showing a checkbox to accept terms & conditions at user sign up. Instead, we'll include a disclaimer that says the user is accepting the terms. Organizations who prefer to have a checkbox can configure that from the org admin homepage > Settings > Options > Membership section. †
    • We've updated the New Account page to have the first and last name on the same line for larger screens. This reduces the length of the user account creation form. For smaller screens, the fields will still stack. 
    • We've tweaked the styles of section separators on the New Account and Login pages.
    • We've updated the admin invitation workflow to ensure that a team invitation can be accepted by using the Facebook Login or Google Sign-In feature.
    • We've fixed a bug where existing users added to a team needed to sign out and then in again to see the admin link in their user navigation menu.

Updates / Bug Fixes

• Updated translations. Thank you as always to all of our translators!
  
  
• We've fixed an issue where the cookie consent banner was introducing a horizontal scroll on mobile devices.
  
  
• We updated the disclaimers for custom fields to automatically display directly below the custom field, instead of below the sign/RSVP button.
  
  
• We've fixed a bug that was preventing partnership admins from editing their events/petitions.

Petitions

New

• We've updated the petition creation process. Now, when a partner admin clicks the Start a Campaign link in the header (or the button on the homepage), we'll include a prompt on the form asking them if they want the campaign to be associated with their partnership. If they are only the admin of one partnership, this will be displayed as a toggle (and they can switch the toggle to no if they don't want the campaign to be part of the partnership). For users who are partner admins of more than one partnership, they'll see a dropdown menu that includes all of their partnerships.
  
  Regular (non-partner-admin) users, will also see the partnership toggle, if they're viewing the partnership's public hub page and then click the Start a Campaign link in the header (and if the partnership is configured to accept petitions from members of the public). As with partner admins, the toggle will default to yes, but it can be toggled off, if the petition should not be associated with the partnership.
  
  We've rolled out this change in response to feedback about partnership petitions being accidentally created outside of the partnership and then not moved into the partnership until after users had already begun to sign the campaign (which means that those signers are not shared with the partner). †

Updates / Bug Fixes

• We've fixed a bug that occurred when users clicked a map marker on an Effort's map-based lookup page. Instead of showing the user that decision maker/petition, the lookup page would just reload.
  
  
• We've fixed an issue where the Decision Maker Form customizations section was not visible on an Effort's Leadership settings page.
  
  
• We've released a fix for glitchy creation date sort order on admin petition lists.

Events

New

• We've updated the event creation process. Now, when a partner admin clicks a Host an Event link in the header (a link to /events/new, which can be added to the site's header from the org admin homepage > Settings > Branding > Configure header and footer), we'll include a prompt on the form asking them if they want the event to be associated with their partnership. If they are only the admin of one partnership, this will be displayed as a toggle (and they can switch the toggle to no if they don't want the event to be part of the partnership). For users who are partner admins of more than one partnership, they'll see a dropdown menu that includes all of their partnerships.
  
  Regular (non-partner-admin) users, will also see the partnership toggle, if they're viewing the partnership's public hub page and then click the Host an Event link in the header. As with partner admins, the toggle will default to yes, but it can be toggled off, if the event should not be associated with the partnership.
  
  Similarly, users who are viewing a calendar hub page when they click the Host an Event link in the header will see a toggle asking them if they want to associate their new event with the calendar. This toggle will default to yes, but it can be updated if needed. 
  
  We've rolled out this change in response to feedback about calendar events being accidentally created outside of the calendar and then not appropriately included on the calendar's hub page. †

Updates / Bug Fixes

• We're now syncing shift information to EveryAction/NGPVAN
  
  
• In addition to featuring ControlShift-native events, admins can now also feature external events. For organizations using MobilizeAmerica, high-priority events will be automatically featured.
  
  
• We've added ordering options for an event host's attendees list. This allows hosts to sort the attendee list alphabetically or by the recency of the RSVP. We expect this will make it easier for hosts to check in attendees  at events. †
  
  
• We've removed a setting that allowed organizations to prevent hosts from hiding event addresses at the organization and calendar level. Now, all event creators will be able to hide their event's address.
  
  
• We've released a fix for an issue where toggling the Statistics panel in an event's admin Attendees tab would cause the panel to flash open and immediately close.
  
  
• We've fixed a bug where some members who had RSVPed to an event were unable to unsubscribe from event updates.
  
  
• We've fixed a bug where when trying to create a blast email for an unlaunched event, users would see an error page. Now users will be prompted to launch the event instead.

Nothing new in groups or VisitThem. 

† 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.