Safer event copies, steadier ticket setup, and simpler hub admin

Copy an event, then review it

Duplicating a ticketed event now brings its reusable setup together in one new draft.

Dates, bookable times, regular ticket choices, prices, sales batches, limits, and forms are copied.
The new draft opens on Tickets so you can check the schedule before publishing.
Staff, orders, and tickets already issued to people stay with the original event.
If an older ticket setup cannot be copied safely, Hubbaly creates nothing and tells you what to review.

The schedule helper starts from the event date and time. Late sessions can continue into the next day automatically.
Your draft stays in place when another organiser makes a harmless ticket change. If the saved schedule itself changed, Hubbaly keeps your work visible and asks you to reload.
Save Changes stays within reach on phones, even after the schedule section is folded.
If a new unused ticket appears while you work, you choose which time keeps it before copying its setup to the others.
Buyers keep an unchanged fixed-time ticket after a checkout refresh and are not asked to confirm the same price twice.
A buyer who fixes their email before paying keeps their saved ticket choice.

Photos, whether to keep original videos, and defaults for new events now live in Hub Settings.
Questions you collect from people and their answers now sit together in People.
The old Advanced area has gone; old links lead to Settings.
Each chat channel now controls whether its photos and videos go to an album. The old hub-wide switch and current-location message are gone.
Email Studio, sender settings, questions to collect, and staff roles are available without upgrade prompts. Normal permissions and real usage limits still apply.
Manage Event opens Sales once the first ticket sale begins. Before that, it opens Tickets.

Owners, admins, and managers can select a person’s name in Event Sales or Event Day when Hubbaly can match them to a Hub People record.
Only the name is a link. Order references, ticket actions, and other row controls still do their own jobs.
Staff-only views and people without a matching Hub record continue to show plain text.
When you remove a hub member, active-ticket follow-up links stay visible. The confirmation also explains that returning needs a new approval or invitation.