✅ New Features
When in an event and viewing a contact's profile, you can now:
- Add or remove portal access
- Change the username a contact uses to access your event portal
- Send a "Reset Password" email to the contact in the case they forget their password
2) Toggle opening portal files in new window:
When adding files to portals, you can now choose if you want a specific file to open in a new browser tab when a user clicks it -- or have it open in the same page via modal (current functionality).
-
✨ Enhancements
1) Twitter is now X:
The standard field "Twitter URL" is now called "X (Twitter) URL"2) Improved handling of Imports when Unique Contacts is enabled:
When you have Unique Contacts enabled for your Organization, importing contacts will now validate the contact email addresses you are importing against existing records across your organization. We will flag the imported contacts that we can't process due to the email address already being used.3) Sorted Sessions in Document Generation:
When using sessions in Document Generation, your sessions will now always be sorted in ascending order by the session "Starts At" date. 4) Edit Custom Field Details:
You can now edit the name, description and max length of custom fields when editing them. Previously, this had been disabled after creating new custom fields.5) Jump to quick filtered views from your CRM Dashboard:
For Speaker CRM users, you can now click on the names of "Companies" and "Areas of Focus" (aggregated session tags) to jump to a filtered view of contacts across all of your events that match the selected criteria.
-
🔗 Integration Updates
1) New Swapcard Configuration Option:
When creating or updating "People" records in Swapcard, we now use the
"force: true"
option by default. This helps eliminate issues that some customers have been encountering when having multiple events under a single Swapcard community and existing people associated with many events. You can read more about how Swapcard handles this option here.
-
🐛 Bug Fixes
1)
When generating files in Document Generation, it will always use your primary event language (defaults to English). Previously it would use one of your secondary languages.2)
When importing values to Dropdown fields and values have commas in them, you will now see the data import as expected. Previously there was an edge case where this condition would cause specific values not to be imported.