Skip to content

🌟 Make the "Copy my details to attendees" checkout control toggleable per event from the dashboard #1217

@giuliosmall

Description

@giuliosmall

Is your feature request related to a problem? Please describe.

During checkout, on the attendee-details collection step, Hi.Events always shows a "Copy my details to:" control (rendered as a None / First attendee / All attendees segmented control when there are multiple attendees, or a "Copy details to first attendee" checkbox when there's a single attendee).

This is currently always visible. There's no way for an organizer to turn it off. For some events this is undesirable:

  • Events where every attendee must enter their own distinct information (e.g. names printed on badges, per-attendee dietary/accessibility data, age verification).
  • Organizers who find that buyers click "All attendees" out of convenience and end up with duplicated/placeholder attendee data, which then needs manual cleanup.
  • Events that want to enforce data quality / per-attendee accuracy.

Today the control's visibility depends only on order composition: orderRequiresAttendeeDetails && !isPerOrderCollection && totalTicketAttendees > 0 , and not on any organizer controlled setting.

Describe the solution you'd like

Add a per event boolean setting (e.g. allow_copy_details_to_attendees, default true to preserve current behaviour) that organizers can toggle from the event settings dashboard. When disabled, the "Copy my details to…" checkbox/segmented control is hidden from the checkout flow.

This fits naturally alongside the existing checkout related toggles (e.g. the "Show marketing opt-in checkbox" switch in Homepage & Checkout Settings).

Additional context

The existing allow_attendee_self_edit setting is a good reference for the full pattern this would follow (DB migration on event_settings, generated domain object, UpdateEventSettingsDTO + request validation, organizer + public EventSettingsResource, frontend EventSettings type, a Switch in the settings section, and one visibility condition in the checkout CollectInformation component).

I'm happy to open a PR implementing this if the maintainers are open to the feature. 🙂

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions