All updates

Member imports, pictures in event updates, and membership decisions

Bring across a member list, place pictures between paragraphs in an event update, review applications privately, and guide ticket holders through forms and transfers.

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

Import your member list

  • 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.
  • Each person receives their own invitation, reviews their details and the hub terms, then decides whether to join. The import does not add anyone automatically.
  • Invitations use the hub banner, logo, and name. Newcomers create an account from the invitation, while people with an account sign in.
  • Each person reviews the shared details from their own import row. A completed link opens an Invitation already used page.
  • The import page tracks progress and shows when you can send an invitation or reminder. The Member Import guide explains how to prepare a list and what members will see.

Membership records and decisions

  • Owners and admins see membership applications and private imported records together on each person’s Hub People page.
  • Private hub records are visible to owners and admins. The person and hub managers do not see them.
  • For a rejection, write a private review reason and a separate message for the applicant. Choose whether to send the outcome by email and alert, or record it without a message.
  • Applicants with an account can open their outcome. Owners and admins see the decision history, and a new application carries a warning when the same account was rejected before.
  • Applicant names link to the matching Hub People record. Approval emails for account holders include Open hub.

Event team roles

  • Event co-organiser roles provide access to setup, sales, messages, team, reports, private answers, and event controls without granting hub-wide management access.
  • Use Start with Event co-organiser as a starting point, then adjust the role for the job.
  • Event staff see the tools included in their role, such as Event Day, tickets, attendance, and incident work.
  • Read-only sales access includes totals and order activity. It does not include buyer contact details, refunds, or exports.

Pictures in event updates

  • Use Add image to place a picture at the current writing position. One update can contain several pictures with text between them.
  • Select a picture to move it earlier or later, edit its description, or remove it. The controls work by touch and keyboard, stay above phone navigation, and include Undo after removal.
  • Preview and posting wait for every upload to finish. The app and email keep the same picture order. Phone alerts, Alerts, and email inbox previews use the written message. A picture-only update says Open to view the update. and links to the full update.
  • Communications lists an update as soon as it is posted. Required-document messages record their audience and delivery results, and each record opens the full recipient list.

Ticket sales, forms, and transfers

  • Use Cap at current sales to set one ticket’s limit to the places already sold or held. Returns and waiting-list offers can reuse a place, and Remove cap restores normal sales.
  • A ticket with no remaining places says Sold out. An earlier sales phase says Sold out for now when another phase is scheduled. A place in someone else’s checkout says it is being held.
  • Organisers can correct a ticket name after sales. Live tickets use the edited name, while completed orders and financial records keep the name used at purchase.
  • Ticket and Event Day summaries count forms for the current owner and active guests. Review forms opens the ticket-level list of work still due.
  • A members-only transfer explains that the recipient needs a free Hubbaly account and hub membership, and provides a hub joining link to share. Public events offer Send by email when no matching person is found.
  • Open order from Hub People goes to the matching order, including when compact order references look alike.

Alerts, account steps, and support

  • A ticket transfer to a Hubbaly member appears in their Alerts. If phone notifications are enabled on their device, it can also send a phone notification.
  • For a public-event transfer sent to an email address, an existing Hubbaly account for that address also receives the alert. The secure email link works with or without an account.
  • Login and registration check for an existing session when an installed app or iPhone browser tab returns to view. Someone already using a password, passkey, invitation, or paid-signup link continues to the page for that route.
  • The email verification page starts with Check your inbox, checks automatically, and includes resend, sign-in, and recovery choices.
  • Get support here appears first in Settings under Support. When WhatsApp support is available, it opens the Hubbaly conversation with a prepared message.

Public hub pages and downloads

  • A private hub page gives signed-out visitors one access prompt and lists any public events or photos from that hub.
  • When a hub has no public events, its public event page says so.
  • On iPhone and iPad, photo and album downloads save the original files, including every part of a large album. If a save is interrupted, Hubbaly stops before creating an empty or incomplete file.

Behind the scenes

Member import source files are private and deleted after one day. Communication history records queued and completed delivery, and delivery tools distinguish blocked addresses from optional-email choices. Production monitoring retains server-lifetime metrics and log history. Pull-request checks run in parallel with the full release test set.

Keep up with what we ship

Follow new releases by email or feed.