v1.3.3 — Registration Tile Customization, Community Feed Privacy & Finance Reliability
Version: v1.3.3
What Changed For Your Team
This release extends what organizers can say on each registration type tile — custom subtitle and description copy now appear below the tile name when attendees choose their ticket. It also fixes several registration workflows: registering on behalf of another person now carries the correct attendee identity all the way through to later changes, group checkout drafts survive navigation without overwriting unsaved answers, and the financial screens that follow a registration make it clearer whether a balance is available credit, a proposed refund, or a completed one.
The community feed has been tightened so that posts, reactions, and uploads are visible only to people registered in that event's project. Finance payment and receipt lists recover from the intermittent database errors that appeared on busy events. Staff sign-in is more stable across concurrent requests and after system updates.
Highlights
Custom Copy and Images on Registration Type Tiles
Organizers can now add a subtitle and a longer description to each registration type, giving attendees more context when choosing their ticket. For example, a Full Conference tile can say "Includes all plenary sessions, workshops, and the gala dinner" while an Online Access tile can say "Live stream and recordings — no in-person access".
Tile images also have a new Cover fit mode: the image fills the tile area without letterboxing, producing a more consistent look when ticket images have different aspect ratios.
Find these settings under the Appearance tab when editing a registration type. See Registration Types.
Community Feed Access Limited to Project Members
The community feed — where attendees can post, react, and share files — now enforces project membership. Only people registered in the event's project can see and interact with the feed. Staff and admins who do not belong to the project are not affected, because admin access continues to work as before.
Attendee email addresses visible within the feed are now shown only to staff who already have access to the registrant list.
This change takes effect automatically. No configuration is needed.
Detailed Changes
Registration
- Organizers can add custom subtitle and description text to each registration type tile. The copy appears in the tile on the registration wizard and in the detailed type information panel.
- Tile images can be set to Cover fit, filling the tile area without visible borders.
- When staff register on behalf of another person, the attendee's identity is now preserved through checkout and any later changes such as transfers, amendments, or cancellations. Previously the on-behalf prefill could be lost if the form was saved or the session was resumed.
- Group checkout now restores each group member's saved form answers when returning to a draft, without overwriting edits that were in progress.
- Dietary requirement answers that exceed the previous short-text limit are now stored in a longer text field. Existing long answers will no longer be silently truncated.
- Admin-created registrations retain the intended attendee's identity when staff complete the form on their behalf.
Finance
- Finance payment and receipt lists (including registrant financial summaries and invoice views) no longer fail intermittently with a database error on events with large volumes of transactions. The underlying query pattern was rewritten to batch finance context once per page rather than once per row.
- The financial screens that follow a registration change now clearly distinguish between available credit (money the organizer owes back), proposed refund (a refund that has been calculated but not processed), and completed refund (a refund that has been paid out). Previously the same balance could appear under more than one label, leading to confusion in high-volume refund workflows.
Event Site Pages
- Event-site pages that include a Flexible Hero block with no saved image alt text now render correctly. Previously these pages showed an error rather than the page content. If you have pages with a Flexible Hero, they will work correctly without any changes on your end.
Community Feed
- Posts, reactions, uploads, and @mentions in the community feed are now restricted to people who belong to that event's project. People who are not project members can no longer interact with the feed.
- Within the feed, attendee email addresses are now visible only to staff who already have access to the registrant list.
Reports
- The report builder live preview and ad-hoc run now return a clear validation message when a saved report definition includes an unsupported filter operator or an invalid segment reference. Previously these conditions produced a generic database error with no indication of which part of the definition needed to change.
Staff Sign-In
- Staff sign-in to tenant portals is now reliable across concurrent sign-in requests. A race condition that could cause intermittent failures when multiple staff signed in at the same time has been resolved.
- Staff signing in through a tenant's platform-level login page now land in the correct tenant portal rather than being redirected to the platform admin page.
- Signing keys that verify login tokens now persist across system updates and container restarts. Existing staff sessions and account links are not affected.
What You Need to Do
No action is required for this release. All changes take effect automatically.
If your event uses the community feed and previously allowed posts from participants who were not formally registered in the project, those participants will no longer be able to see or interact with the feed. This is expected behavior and no configuration is needed.
Additional Improvements and Fixes
- Terms and conditions presentation in the registration wizard has been cleaned up; redundant layout elements that appeared when no custom terms were configured are no longer rendered.
- The Managed Registrations detail view in the attendee portal now correctly shows form sections for managed registrations, resolving a case where required forms appeared blank.
- Staff who belong to multiple tenants will continue to have their accounts and sign-in methods preserved following the migration of staff SSO to a maintained auth framework.
- Room management capabilities are being built out in this release cycle. Room data and AV details can be managed in the ema API; the room admin interface is coming in the next update.