We also fixed some minor spacing issues on the Settings > Options page.

This behavior was already available for organizations with the “obfuscate member existence” setting enabled. This update extends that behavior to all organizations.

More details in our developer documents.

We’ve now reset the “last updated at” timestamp for petitions whose most recent update was the automatic conversion, setting them back to their previous content updated timestamp.

Please note that organizations may wish to update customized event email templates to include notes about unconfirmed locations. More information.

This updated behavior requires contact messages to be enabled and the Mailgun integration to be active. We’ve reorganised the admin page where contact messages and other messages for a petition are shown to include replies from petition signers.

This setting used to apply to partner and petition blast emails – it now only applies to partner blasts.

Email replies will be sent to a tokened email address to protect the host’s privacy. This functionality applies to: the thank you for RSVPing email, edited event/shift notifications, reminder emails, and blast emails from a host to their attendees. This functionality requires that contact messages are enabled and uses the Mailgun integration. More info.

Group organisers can also now export a CSV of their group members from the manage Members tab, which will use the organization’s name and contact info privacy settings.

We now explicitly ask the user to reload the page to ensure that it will succeed the next time.

We ran an a/b test on the sharing modal, and we found that including a web share API button in the modal increased share conversions by 3%.

More information on Friendly Captcha is available on their website: https://friendlycaptcha.com.

It will now be appropriately displayed for users with the Events Admin View permission.

Organizations can also customize the footer text block that’s used for individual partnerships using the Modern email layout.

Contact messages are now visible to admins with the appropriate permissions in the admin view of the group/event and in the platform-wide Inbox.

In particular: - Webhooks and API responses that include petition, group, or decision maker locations no longer include a “venue” field for those locations. - The CSV export of decision makers in an effort no longer includes a “venue” column.

This update allows organization staff to track their action opt-in rate per email sent from Action Network.

This update makes rich text content available in the: - Petition’s and Petition Start’s what and why fields - Blast Email’s body - Partnership’s introduction text - Group’s resources

More info: https://developers.controlshiftlabs.com/#bulk-data

This allows organizations to set up custom workflows for petition flags.

Information about the shifts they previously signed up for will not be made visible for privacy reasons, but a list of all of their shifts will be include in the thank you for RSVPing email.

We recommend using this method for new connections. API keys can also be used to replace existing OAuth2 connections. More information is available in our developer docs: https://developers.controlshiftlabs.com/#authenticated-rest-api-getting-started.

This change is to make the UI clearer for events with shifts happening on multiple days.

These updates include: performance improvements, new links to the petition each comment belongs to, and removal of redundant buttons for approving already-approved comments or removing already-removed comments.

This prevents performance issues for petitions with many updates that include embedded content.

We also fixed a bug that showed a user a generic error page if they attempted to accept a team invitation from a team that was since deleted.

The new list can be found at Settings > Teams & Permissions > Pending invitations.

We’ve also updated up the “Save” button behavior on the comment form to avoid accidental double-clicks.

Thank you to the 350.org team for providing this translation.

Previously we’d send the email from “via [Organisation Name]” which only makes sense when there’s an actual leader included in the string (“[Petition creator] via [organization name]”). Now we’ll just use the Organization Name if no leader is included in the string .

We’ll no longer show an error in the moderation queue when a message is deleted while still pending moderation. We won’t display the first message of the thread in the Topics view if it’s still pending moderation. We’ve fixed some edge cases where messages pending moderation could be displayed to other members.

We’ve also fixed a bug in the location-based group creation workflow that prevented the searched location from carrying over to the form if the user had to log in on the way there.

For groups, messages are submitted to the moderation queue and hidden to other members until moderated. For events, messages are automatically hidden.

Ejected members will be shown in the “Removed Members” list on the group’s admin pages.

For users who have not completed our GDPR DPA, you shouldn’t see any changes in services. For organizations who have a completed DPA, your organization will no longer need an external Mapbox/Geoapify account. If your organization had not already integrated with one of those tools, your supporters will now be able to see the /local page and maps on other lookup pages.

This option allows admins to specify a logo, set a background header color, and choose fonts to be used in emails sent from the partnership’s email supporters tool on the partner hub page.

The list of names will use the organizer name privacy setting configured by the organization.

Because the “slug” is required for uploads, this will make it easier to import events into a decision maker calendar.

Previously members would be able to see the new event form page but weren’t able to submit the new event without an error. Now, we’ll show the “Host your own event” only if there’s an unclaimed target within the search radius. If all targets in the search radius have already been claimed, we won’t show the “Host your own event” button.

The variable returns the ISO 3166-2 region code associated with the postal code entered by members.

After configuring a new post-action flow, it can be added to the URL using the after_action parameter. More information is available in our help center.

This is an option setting that can be toggled from the GTM integration’s settings page. When enabled, user’s email addresses will be added to the GTM data layer for use with Google Ads

To sign in to ControlShift with Google on your phone, access the site via a regular browser app such as Firefox, Chrome, or Safari.

This unlocks new ways of organizing events with coalitions of partners. Events created in a multi-partnership calendar will be associated with multiple partners.

As part of those updates, anyone trying to send a message to a petition creator, event host, or group organiser through the site will now need to confirm their email address before the message is sent.

The events will be displayed on a partner-specific map. The petitions are now displayed in a swipeable carousel and successful petitions will be designated as such.

Authenticated API responses that include signature information now also include information about messages to decision makers where appropriate.

We’ve also fixed an issue that prevented making updates to events in certain calendars.

Partnership settings that used to be on the Edit page are now found in Settings > Basics.

When a campaign is in multiple partnerships, the campaign page will show the titles and opt-ins for all its associated partnerships, and each partnership’s hub and admin pages will include the campaign. Options for showing signature opt-ins are available, and you can learn more in our help center.

This includes updating their partnership’s name, description, and logo.

The classic layout remains the same. The new option has a logo and background banner at the top of the email.

Org admins will be able to see a copy of the message in the organization’s inbox, but it will not be delivered to leaders.

This error occurred when the partnerships had over 10k different actions from members.

Event pages will now more closely resemble petition pages. Partner organization information will be show closer to the top of the event page while other associations have moved down.

Previously, if a petition had multiple associations, we’d only show one link to site visitors. This would mean that users might, for example, only see information about an effort and not see info about a partner org or local group. With this change, all associations will be shown at the bottom of the page with partner organization information prominently featured near the top of the page.

Also, it no longer includes the superfluous “id” column.

Also, on filterable lists of events, petitions, and groups, the sort options are now alphabetized correctly for the user’s language

Team members who can “admin view” events can now see the Associations section on admin event pages, even if they do not have permission to change the associations.

Petition and event image can also be uploaded during moderation. We’ve also fixed an error that froze the browser tab while attempting to crop petition and event images while moderating.

If you’ve customized the reminder templates (Settings > Content > Events), you may need to update the template’s text to reflect this change.

We’ve also fixed petitions’ and events’ associations widgets layout to improve how they’re displayed in different screen sizes.

This change allows organizations to use host variables in the: - Attendee confirmation email - Thank Attendee RSVP Email - Promoted from Waitlist to Attending Email - Approaching Event Email Reminder for Attendees This applies to organization default templates, custom calendar templates and custom event templates. Valid attributes for the host are: first_name, last_name, full_name, email, postcode, phone_number, locale, and country.

This should improve the appearance of campaign and event pages, while also avoiding copyright infringement on member-led campaigns.

Our previous minimum requirement was six characters. Existing passwords that are 6-7 characters will remain valid, but we’ll require more than eight characters for new accounts and for users changing their password.

The public JSON endpoint for an effort now includes the ended_story for all petitions marked as ended, not just petitions marked as successful.

This will be phased in for newly-used locations first. This change includes using localized map labels, not just labels in English.

The hCaptcha integration is available in Settings > Integrations. This is a third-party integration, and requires an hCaptcha account. The integration will work with both visible and invisible challenges, depending on the settings in your hCaptcha account. More information

This new toggle is available in Settings > Privacy.

We fixed a similar bug for admins viewing the event page that, on mobile, sometimes hid part of the “Upload image” modal behind the RSVP button.

This content and the “Training” label can be customized under Settings > Content > Events.

This content and the “Training” label can be customized under Settings > Content > Petition Manage.

For events that have no image or default image to display, the host view of the event page also now includes a large prompt asking the host to upload an image.

This banner will be shown after the user dismisses the “just launched” social sharing banner and will persist until the items are completed. The banner will not show for petitions moderated to suppressed or below.

This may be useful for organizations supporting primarily virtual events. The list-only embed option is available under Settings > Local Map.

This matches the behavior we use on event lookup pages and petition signature pages. Once an event reaches 5 attendees, the attendee count will be publicly visible.

The new additions include: Canada, New Zealand, South Africa, the Netherlands, Sweden, Belgium, Austria, Norway, Germany, Luxembourg, Denmark, France, and Romania.

This button is available for some CRMs under Settings > Integrations.

When creating or updating the Google Analytics integration, please choose either GA4 or UA from the Settings > Integrations > Google Analytics page.

For events that don’t have an end time set, we’ll keep the event in public listings until 2 hours after the event began.

More information about this change is available.

In particular: - When a petition has custom “Thanks for signing” email content, we’ll now check the syntax of any Liquid markup in the custom content. - When a partnership customizes the “Thanks for signing petition email”, “Thank Signer Forward to Friends Email”, or “Share By Email body text”, we’ll now check the syntax of any Liquid markup in the custom content.

We’ve also tightened the enforce 2FA setting. Previously, we were prompting users to set up 2FA during log-in, but they could navigate to another page if needed. Now all admins (org admins and partners) will be unable to navigate away without configuring 2FA.

We made this update following an a/b test of static vs. animated progress bars, where the animated version increased conversions.

Users newly enabling two-factor authentication will experience the TOTP method of two-factor authentication.

After providing cookies consent, users can navigate to /member/revoke_cookies_consent to revoke their consent.

The new event is Loaded another promoted petition. You can find all platform events in our help center.

The other rules of promoted petitions will still apply, but a user is able to click “Show me another petition” if there are additional campaigns that they could sign.

When a petition is added to the promoted petitions list, admins can now add label restrictions. When set, the promoted petition will only be used if the petition the member just signed includes all the labels in the restriction. This can be helpful in more closely targeting what petitions signers see after taking action. The other rules for promoted petitions will still apply.

ControlShift now includes Cloudflare proxying for your ControlShift site. Because we’re managing the Cloudflare configurations, you’re able to benefit from Cloudflare’s features without having to deal with the technical details. Cloudflare is an industry leader in Distributed Denial of Service (DDoS) attack and malicious bot protection. Cloudflare uses sophisticated machine learning to protect sites from malicious activity, while also accelerating the delivery of page content.

More information is available in our help center.

We’ve fixed an issue with the public JSON API for listing petitions in an effort, that could sometimes cause extra petitions to be erroneously included.

Also, when new non-ControlShift hostnames are added, traffic on those domains will now be protected by Cloudflare proxying. ControlShift manages this proxying automatically, so no extra steps are needed.

We also improved UX for the moderation modal close button when a field is being edited.

We plan to release an update supporting GA4 in the future.

These improvements include support for organization-wide and per-petition custom fields and consistency between the fields displayed on the web form and in the bulk entry tool.

The links for messenger sharing were being stripped out of emails by certain email providers, including gmail and outlook. We’ve reimplemented this sharing channel to first send users to the ControlShift platform before sending them on to messenger.

We still strongly recommend that all users keep their browsers (and operating systems) up to date to ensure reliable performance and timely access to security updates.

Please note that this integration option will only appear in Settings > Integrations if other analytics tools have not already been configured.

We still recommend that organizations be mindful of the integration’s impact on page load speeds and performance.

Also, when a member is signing via an embedded signature form, validation errors will now be shown within the embedded form. The member will only be redirected to the petition page once their signature is successful.

Organizations can choose which SMS opt-in a site visitor experiences by setting a sms_opt_in_type_id URL parameter by using the SMS opt-in type’s ID number.

This is not a self-service feature, so please contact us if you’re interested in setting up the one-click mapping feature.

To enable this setting, go to the org admin homepage > Settings > Social Media, click the pencil icon next to WhatsApp, and check the “Also enabled for non-mobile devices” checkbox.

With this work:

• All visitors to petition pages should now see the updated styling around the signature form.

• We’ve also fixed a bug that could, in rare cases, prevent a logged-in user with invalid profile information from signing petitions

With this improvement, logged-in users and users with a “recent action” (a recent RSVP or signature) in their cookies can RSVP to additional events with one click.

We also fixed a related bug that caused an error when leaving a comment if the name privacy setting for action takers was set to “no display.”

We’ve also improved the the styling for the “Sign with Facebook” button on tablet-sized devices for certain locales that made the content not fully visible.

We’re now hiding sharing channel names (relying on icons instead) to preventing text wrapping.

This icon will not be displayed if the organizer has messages from the public disabled.

This work also included restyling the message shown after RSVPing when email confirmation is required.

We’ve also improved the error messaging shown when a user tries to save an in-person event without entering a location.

See more details in our developer documents.

This can now be configured in the Sharing Channels list for each channel.

The new settings are available by going to the admin homepage > Settings > Social Media. At the top of this page, you’ll see the social share options that are currently enabled and their current order. From there, admins can add and/or remove social media options or change the order in which these buttons are shown.

Updates to the order of the buttons will be reflected in the ‘share on’ box on petition and event pages, the post-action social share popups, and any emails using the {% social_share_buttons %} or {% blast_email_social_share_buttons %} variables.

Previously, we were showing the html for the character (e.g. ') instead of the character itself (e.g. ').

This will only affect petitions that were drafted, but not launched, before we updated the petition creation flow. This also does not affect effort petitions, where the Launching page is still part of the process.

More information about these bulk data exports is available in developer documentation.

We encourage all admins to enable two-factor authentication for their account. With this update, all admin accounts not secured with two-factor authentication will be shown a warning on the admin dashboard. Organizations can also update their settings (in Settings > Options) to require all admins to enable two-factor authentication.

When sending users to calendar, effort, or landing page lookup pages, you can now include utm_campaign, utm_content, utm_medium, utm_source, and utm_term parameters in the URL. (Example) These parameters will then be included in the petition/events’s Admin > Tech Bits section and CSV exports from the admin petitions/events list pages. This can be useful for tracking activity from ads, emails, or other activities.

Organizations using the old individually-styled social share buttons should have already been updated to use the new {% social_share_buttons %} variable. This variable can be used in any blast email template included in Settings > Content > Blast Emails, and will automatically insert Facebook, Twitter, and optionally, WhatsApp buttons.. We’ve also added social share prompts to our default content for the templates that didn’t have them previously.

This fixes an issue that could previously occur where the petition creation could get “stuck” and the first signature would not be created

If your organization has not customized the text of the default blast email templates, you’ll see the updated template text automatically. If your organization has made customizations, but you’re interested in reviewing the updated text, just send us a support email.

This new experience makes it easier for campaigners to see the optional templates without needing to scroll to the bottom of the page.

Organizations can update their existing templates to use the {% social_share_buttons %} variable instead of separately styled buttons.

When sending users to event and petition creation pages, you can now include utm_campaign, utm_content, utm_medium, utm_source, and utm_term parameters in the URL (example). These parameters will then be included in the petition’s Tech Bits section and CSV exports from the admin petitions page. This can be useful for tracking activity from ads, emails, or other activities.

Associating a partner with a theme allows admins to control the look and feel of that partner’s hub page and event/petition pages. Previously these pages needed to match the rest of the ControlShift site, but now they can be customized to have their own colors/fonts/logos/links. This feature could be used to co-brand with a partner and to provide links to the partner’s main website on their ControlShift pages.

Associating a calendar with a theme allows admins to control the look and feel of the calendar’s host recruitment and event pages. Previously these pages needed to match the rest of the ControlShift site, but now they can be customized to have their own colors/fonts/logos/links. This can be useful for days of action that have their own sub-brand that’s distinct from the organization’s main brand or for a calendar of events being cosponsored with a partner.

Associating an effort with a theme allows admins to control the look and feel of the effort’s recruitment and petition pages. Previously these pages needed to match the rest of the ControlShift site, but now they can be customized to have their own colors/fonts/logos/links. This can be useful for campaigns that have their own sub-brand that’s distinct from the organization’s main brand.

Preset filters are used on admin list pages (petitions, events, and groups) and can be useful if an admin is often adding the same set of filters to these lists. With this update, admins with Configure Settings can create preset filters and share them with the rest of the organization. Users can now also delete their preset filters.

This is useful for organizations with more than one hostname, and it allows users to remain on the same hostname when being redirected to a new page.

To receive emails when a new or updated petition requires moderation, subscribe to the “Petition Created Requires Moderation” or “Petition Updated Requires Moderation” notifications.

Events and petitions are automatically approved if they’re created by a group organizer and associated with a group or if they’re created in a calendar that’s set to automatically approve events. Users creating these petitions and events will now be shown the ‘just launched’ screen instead.

Admins can specify the search radius (in km) for event pages from Settings > Options > Events.

Previously it was possible to view these messages, but not possible to filter them to a specific event. To view the list of emails for a specific event, go to the event’s Admin page > Blast Emails.

The Themes feature allows organizations to customize the fonts and colors used on the platform. Support for multiple themes will allow organizations to use different fonts and colors on specific parts of the platform, including things like partner/coalition campaigns and events, days of action, or other special campaigns.

(Phone number information was previously added to Action Network as a custom field on the user record, but we’re now syncing that information to the official phone number field.)

When information is retrieved via the API about a petition, event, or group, it will now also include information about a mentor if one is assigned.

When a main effort is set, new petition prompts in the platform will point to the effort’s new petition page.

More information is available in our developer documentation.

More information is available in our developer documentation.

This allows admins to add variables like: facebook_share_url, twitter_share_url, whatsapp_share_url, etc. to the default email that’s shown when a petition creator or event host goes to their email supporters page. The text of the default emails can be edited from Settings > Contents.

We’re now truncating these too-long texts.

More information is available in our developer documentation.

We’ve also fixed a bug in event moderation that could, in rare cases, prevent an updated location or virtual event audience from being saved.

For organizations using email confirmation for actins, members who click through a signature/attendee confirmation email, sign a petition via an embedded form, or sign using Facebook will now end up at a non-tokenized petition/event URL that is easier to copy/paste and share with others.

In particular: Members who have to confirm their email address after RSVPing to an event will now experience the post-RSVP daisy chain after clicking through the confirmation email. Also, we’ve fixed a bug where members who signed petitions with Facebook and did not need to provide additional information did not experience the post-signing daisy chain.

With this update, the image is simply not rolled back, but the rollback otherwise succeeds. Rolling back to an old version with no image also removes the image.

More information about ControlShift’s Slack integration is available.

In particular:

• In event moderation, the Location field now uses the same Virtual/In-Person buttons as the event form

• We’ve fixed a bug for in-person events where the state/region field was missing from the event form in some countries

• The location field for in-person events will now use the country and/or bounding box configured in Settings > Time Zone & Locale to prioritize location suggestions.

• We’ve fixed a timing issue that sometimes caused an incorrect time zone to be automatically chosen when setting the audience location for a virtual event.

More information about the new petition creation experience is available.

Events will now will be correctly launched once the user confirms their account.

We’ve also fixed a bug on the recruit hosts form that caused event timezones to sometimes be set incorrectly.

Previously, if the petition creator opened a confirmation email from a different device than where they created their account, the context was lost about where the user should be redirected to after confirming their account, which may have resulted in petitions not ending up automatically launched after email confirmation.

The redesigned form uses a mobile-first, modern aesthetic that matches the updated petition creation flow. Like the petition creation flow, we’ve also removed the review step for newly-created events – allowing your supporters to launch their events more quickly.

Organizations using Action Network can now automatically sync event, host, and attendee data to their Action Network account. When a user creates or RSVPs to an event, that event will be added to their action history. Similarly, ControlShift calendars will be reflected as event campaigns in a user’s action history.

Creators or attendees of partnership events will be tagged with the partnership information. Finally, users will be tagged as a controlshift-event-creator and/or controlshift-event-attendee depending on their role. More information about the Action Network sync is available in our help center.

Group collections where the groups are associated with point locations can now specify separate default group names depending on whether the group creator has already searched for a location or gone to the group creation form directly. The new settings are available in Local Groups > (your group collection) > Settings > Organiser Signup.

In particular: this fixed a bug that preventing adding certain advanced filters on public-facing event listing pages, and on org admin lists, it’s now possible to close filter typeahead dropdowns by clicking outside them

Especially for organizations using email confirmation, this should reduce petition leader/event host confusion.

The A/B test allows petition creators to request help if they get stuck during the creation process. Previously, these notifications were sent to the organization’s main contact email. Now, admins can subscribe to these notifications from My Account > Notifications.

In particular:

• Deleting an event will now cause attendee.deleted webhooks to be sent for the event’s attendees.

• Deleting an event will now clean up any empty member records for the event’s attendees.

• Deleting an event will no longer delete group memberships that originated with the event.

We also fixed an error with the user account confirmation email that prevented the {{ organisation.name }} tag from being rendered properly

In particular, we added a REST API for adding labels to events and added a basic REST API for listing local groups and the people who have joined them. More details can be found in our developer documentation.

For the Segment integration, all events are now sent from the client rather than the server, improving consistency and allowing all destinations to consume all the events. The “Petition Launched”, “Event Created”, and “Blast Email Authored” events are now sent to Google Analytics, Matomo, and Google Tag Manager when those integrations are in use. (Previously, those events were only available in Segment.)

Customized content for events can also now use {{ event.formatted_start_at_date_time }} and {{ formatted_end_at_date_time }}.

If your organization is running the platform in English, some of your petition starters may see this new flow. With the new flow, if the user tries to move to the next step in the petition creation process without entering any text, they’ll see a box that allows them to enter their email address and ask for help.

The request for help will send email notifications to the organization allowing staff to work with the petition creator. The petition creator will also receive a confirmation email that allows them to return to their incomplete petition to fully launch it. You can see this flow in our recording of our recent office hours.

The new flow sends petition creators through a step-by-step petition creation process to provide more guidance and focus on each petition field. We’ve also streamlined the petition publication process to remove the ‘review’ step. In our testing, this flow increased conversions by 23%! Organizations who have not already done so can update the content used in this flow from Settings > Content > Start petition.

In particular, we’ve added several columns have been added to the all-attendees export (from the Members page). Also, the calendar attendees export has been expanded to include more columns, and several event location columns in this export have been renamed, to make it consistent with the all-attendees export.

If you’re interested in learning more, we’re also hosting an office hours focused on the upcoming workflow change.

On the local organizing map (/local), we’ve updated the details popup when there are multiple events in the same location, so that the events are ordered from soonest to farthest in the future. We’ve also fixed the layout so that popups with only one item have no scrollbar and popups with multiple items do not have horizontal scroll.

Previously there was a validation that the body was not empty, which prevented you from saving empty content even if the content wasn’t required.

We’ve been a/b testing a new design of the ‘just launched’ banner that prompts petition creators and event hosts to share their petition or event after its creation. The new design increased conversions by over 6%, so we’ve fully switched to the new designs.

We’ve added a Content tab to the petition’s admin tools. This page may include fields that are not available to supporters, and edits made from this admin-only page will not require moderation.

Calendar-wide attendees exports and effort-wide signatures exports will now include the custom fields that have been added to the events/petitions’ RSVP/signature forms.

To use the filter, add ?filter[geography_slugs]=NY,DC to event lookup pages (/events, and calendar lookup pages) or the local organizing map (/local). For example: https://demo.controlshiftlabs.com/local?filter[geography_slugs]=NY,DC. Please note that the slugs are case sensitive. US and Australian state/territory abbreviations are supported when fully capitalized. (Western Australia is written as WAUS to not conflict with the US state of Washington.)

Liquid variables can be used by customers to pass information about the supporter who just took action to your donation platform if that third-party software supports filling in donation form fields like name and email address via URL parameter. The variables should be wrapped in curly braces ({{foo}}) e.g. https://www.example.com?petition={{campaign.slug}}&email={{action.email}}&source={{action.utm_source}}.

The parameters that can be used are: action.email, action.first_name, action.last_name, action.postcode, action.source, action.utm_campaign, action.utm_content, action.utm_medium, action.utm_source, action.utm_term, and campaign.slug.

In our testing, these popovers did not change conversion rates but added unnecessary complexity to the action forms.

We also added information explaining why a campaign creator should upload an image. This work also replaced the design for the modal used to upload and crop images.

The theme feature allows organizations to control the branding of their site independently. Within themes, admins choose the fonts and colors that they’d like to use in various parts of the platform, and these selections can be updated whenever needed. Organizations currently using custom branding can now see the Theme option in their platform Settings page. At the top of the page is a toggle that allows organizations to switch between themed branding and custom branding.

Organizations who are using the iframe step (to collect donations, for example) should see a better-sized iframe modal.

You can use the admin header search instead to get petition and event results in a faster, easier to use workflow.

This was preventing users from adding online conferencing links and extra location details to existing events without also updating the event’s location.

This includes toggles on the all events page (/events), calendar pages (/calendar/foo), and the local organizing map (/local).

We’ve updated the staff admin experience to be easier to navigate and more visually consistent. It’s even easier than ever to find things on your mobile device.

We’ve redesigned the admin petition signature page. The new page makes it easier to clearly see signature sources and makes the design consistent with other lists in the platform.

• It’s now possible to export a CSV of all sources and buckets that have been used with a petition.
• It’s now possible to export a Delivery PDF as an admin, even when this feature is disabled for petition creators.
• We’ve improved the page’s mobile responsiveness.

Updated text displayed in share prompt after signing petitions based on an experiment that showed between 7% and 122% of increases in shares (varying by channel).