All updates

Import your community, share event work, and control ticket sales

Bring across an existing member list, give event helpers only the tools they need, and limit one ticket to the places already sold or held without affecting the rest of the event.

  • hubs
  • invites
  • admin
  • events
  • tickets
  • photos
  • communications
  • trust

Bring your member list across

  • Upload a CSV or text file, paste a list, or enter people directly. Choose the email column, then decide whether each other column becomes a shared member detail, a private hub record, or is ignored.
  • Nobody is added automatically. Each person receives their own invitation, reviews their details and the hub terms, then chooses whether to join.
  • A new member can create an account from their invitation without waiting for a second email verification message. Someone with an existing account signs in as usual.
  • The import page shows progress and results, including when you can send an invitation or reminder again. The Member Import guide explains how to prepare a list and what members will see.

Keep member history together

  • Owners and admins can see membership applications and private imported records together on the person’s hub page.
  • Private hub records are for organiser-owned history. Only owners and admins can see them; the person and hub managers cannot.
  • Owners and admins can export this history or remove an individual private record when it is no longer needed.

Share event work without hub-wide access

  • Give co-organisers the event setup, sales, messages, team, reports, private answers, and event controls they need without making them hub managers.
  • Use Start with Event co-organiser for a ready-made starting point, then adjust the role for the job.
  • Event staff see only the tools their role includes, such as Event Day, tickets, attendance, and incident work.
  • Read-only sales access shows totals and order activity without buyer contact details, refunds, or exports.

Limit sales for one ticket

  • Use Cap at current sales on a ticket card to stop it going above the number of places already sold or held.
  • Buyers see it as sold out, but the ticket stays visible and editable. If a place is returned, it can still go to the waiting list or back on sale.
  • Use Remove cap to let it sell normally again. Other tickets and the event’s sales dates are not changed.

Make alerts and account steps clearer

  • When you transfer a ticket by choosing a Hubbaly member, the request appears in their Alerts and can send a phone notification if they have phone notifications on. They can open it in Hubbaly to accept or decline.
  • For public-event transfers sent to an email address instead, the same alert also reaches an existing Hubbaly account for that address. The secure email link still works for everyone.
  • The email verification page now leads with Check your inbox, checks automatically, and keeps resend, sign-in, and recovery choices clear on a phone.
  • The alert permission prompt no longer interrupts hub creation. You can turn alerts on later from Notification Delivery.

Cleaner public pages and downloads

  • Signed-out visitors to a private hub now see one clear access prompt and only links to public events or photos that actually exist.
  • An empty public event list now uses one short explanation instead of showing controls that cannot help.
  • Photo and album downloads on iPhone and iPad now open the original files more reliably, including every part of a large album. Interrupted saves are caught before leaving an empty or incomplete file.

Behind the scenes

Member imports run in the background, keep uploaded source files private, and delete those files after one day. Private organiser records are kept separate from details members can see, and ticket-transfer alerts do not reveal whether an email belongs to an account.

Keep up with what we ship

Follow new releases by email or feed.