Opening Hubbaly

Still opening. A slow connection takes longer; nothing you had open is lost.

Try again
Skip to Content
Events and tickets

Events and tickets

This guide covers attendee and organiser workflows, with emphasis on event-day reliability.

Event lifecycle (organiser)

1. Draft

  • Answer the five Create event questions. If you have one date and tickets, your first ticket saves with the draft.
  • Use More options for extra dates, artwork, chat, check-in and the other settings.
  • On Tickets, Before this goes on sale shows what is left. Add more tickets and sales phases there.
  • Attach required forms and publish versions.
  • Assign event staff roles and permissions.

2. Publish

  • Publish only when event details and policy are final.
  • Once sales begin, date/time edits should be deliberate and minimal.
  • Visibility and access settings control discoverability and checkout behaviour.

3. Operate

  • Use event admin tabs for Event Day, Scan, Chat, tickets, staff, and updates.
  • On a computer the event admin menu groups its sections under Before, During and After, each in its own colour. On a phone the thin pink bar under the row of sections shows which part of the row you can see.
  • Event Day is the main live roster workspace during an active event and relabels to Attendance records after the event.
  • Scan only appears when the event attendance registration allows QR validation.
  • When scanning is enabled, treat Scanner as the main door tool and Event Day as the broader oversight and records workspace.
  • If attendance registration is off, Event Day stays available as a read-only roster and Scan is hidden.
  • Scanner and readiness checks are canonical and enforce required-form completion.
  • Use overrides only when policy and permissions allow.
  • The scanner stays open for 4 hours after the event end time so late arrivals can still be scanned in. A banner shows while this grace window is active, and the scanner reads as closed once it passes.
  • On a multi-date event, Event Day scopes to one scheduled entry at a time, with a selector to switch. Desk check-in enforces the same safety gates as QR scanning.

Event staff setup

  • Start with reusable staff roles for stable bundles like Door Team, Incidents, or Stage.
  • On a multi-date event, each staff invitation carries the event dates it covers, and access follows what the person accepted. See Staff dates on multi-date events.
  • If one person needs an exception for one event, use Customise access on that staff assignment instead of creating another role.
  • Sensitive permissions such as Verify members and Override required ticket docs can only be granted by owners/admins.
  • If you later remove the exception, reset the assignment back to Role defaults.
  • On a phone, look below a person’s name for labels such as Custom access and Accepted.

4. Close

  • Post final updates where needed.
  • Review attendance and incident outcomes.
  • Resolve refund/void actions deliberately.
  • After the end time, home keeps a Wrap up entry for organisers for 7 days. Events you had a ticket for or worked at move to Past events on home (your last three) and to Account -> Past events, so they stay reachable when photos or follow-up updates arrive later.
  • Anyone still on a waitlist when the event ends is closed out automatically.
  • When you want responses, publish the feedback form and then request feedback as a separate, deliberate step. The request confirms its audience with a live recipient count.
  • Archive operationally complete events.

Create event options

Use Create event when you want to set up a gathering. A new hub opens here on Create event. The form asks five questions and What happens shows what your answers will do.

Core details

  1. What is it called? Give it a name people will recognise on tickets, emails and event lists.
  2. When is it? Choose Starts at and Ends at in London time. Leave them blank if you are only collecting interest and do not know the date yet.
  3. Where is it? (optional) Search for the place if you know it.
  4. Who is it for? Check who can see the event and answer any questions about who can buy.
  5. The first ticket. Keep General admission or name it, choose Free or Paid, and enter a price in pounds for a paid ticket. Leave How many to sell? (optional) blank for no limit of its own.

More options holds settings you can leave as they are. In More dates, and room for everyone, use Add more dates or times when you need a separate schedule. It takes you through Event format, Dates and Review, then Use schedule brings your dates back. Choose Close to keep your unfinished schedule and return to the same stage later. Browser Back moves through the stages first, then asks before leaving an event with unsaved work. Finish or discard any edits to the schedule before pressing Create event.

With more than one date, add tickets after saving, when you can choose which dates each ticket covers. Tickets for one buyer is for a single continuous event. Bookable-time setup asks for Maximum bookings at each time before Preview schedule. You can finish physical capacity for multi-day events and repeated performances in Tickets. For a single date, the number to sell cannot be higher than the room for everyone. If they match, the room sets the limit.

To write a description, open More options, then Description. Choose Add link above the description to link some words, then write the words, paste the web address and choose Insert link. To change a link, tap its words, tap the pencil and choose Save.

Event setup

Under More options, open How people come to change what the form asks.

  • Tickets available now creates a ticketed event. Use it when people should claim or buy a place, receive a ticket, and potentially show a QR code at check-in. This mode requires a start time and an end time before the event can be created.
  • Collect interest first creates an event page for demand-gathering before the date, venue, or tickets are final. People can register interest, but that does not reserve a place or guarantee tickets. Use this for early announcements, wait-and-see venues, or events where you want to email interested people when tickets go on sale.
  • Event-specific interest questions appear on the public Register interest form before the person submits. Use them only for one-off answers needed for this event’s interest list. Put reusable details such as full name or phone number in Hub -> Admin -> People -> Details to collect instead.
  • No tickets for this event creates an event without ticket claiming or checkout. Use it when people can simply attend, or when organisers only need a page, updates, chat, and manual attendance. QR ticket validation is not available in this mode.

Visibility and discoverability

Under Who is it for?, choose Change beside Who can see it for three choices.

  • Hub members only keeps the event inside the hub experience. This is best for private member gatherings or events that should not have a public share page.
  • Anyone gives the event a public event page and makes it eligible for public sharing and discovery surfaces. Public visibility does not automatically mean anyone can get tickets; ticket access is a separate choice.
  • Invited people only hides the event from hub members too. It stays out of discovery, lists, search, and shared surfaces; only invited people and authorised organisers can see it, and anyone else with the link sees “We can’t show you this event” rather than confirmation that the event exists. An invited person who opens the event’s own link while signed in is taken to their invitation. While a published private event has no invitations and no tickets, its admin pages warn No guests can see this event yet, with Invite people.
  • Show attendee list on the event page controls whether the list appears on the event page. When off, nobody sees the list on the event page; you still see everyone in Event admin. Leave it off for more private or sensitive events.

Ticket access

With Tickets available now, the form asks only the questions you need to answer.

  • With Hub members only, hub members can buy tickets. Choose whether every ticket must be for a hub member or members can buy extra tickets for guests.
  • With Anyone, choose Hub members or Anyone, no hub membership required. The second choice lets people buy without joining. If buyers must be members, answer the guest question too.
  • With Invited people only, people book from their invitations. Send invitations after saving.

After saving

Tickets opens after a ticketed event is saved. Draft saved. confirms that only the people who run the hub can see it. If the first ticket could not be saved, the draft stays on Tickets so you can try Add ticket there.

Before this goes on sale lists what you still need to do. A free ticket can go on sale when you publish if there are no other steps left. A paid ticket may need Connect payments and Add your seller details first. Owners and admins can open the relevant settings where they have access. Managers see who to ask. Choose Publish event to open the publish sheet, or Add ticket to set up another ticket.

Refund policy

In Admin -> Tickets -> Rules, choose the refund policy buyers see before paying. You can use no change-of-mind refunds, a deadline for considering requests, or your own wording.

Moving to a cheaper ticket starts as No refund. Choose Refund the difference to return the difference automatically when someone changes their own ticket or session. It uses today’s prices and cannot exceed the money left from that ticket’s payments. The refund is reduced by Hubbaly’s fee and the card company’s percentage on that difference, using the rates actually paid on the original payment. None of the card company’s fixed charge is deducted again. For example, a £20 ticket with 70p Hubbaly fee and 50p card fee, including a 20p fixed charge, moved to £17 returns £2.85. The record shows the refund and 15p kept on the difference. Hubbaly keeps its whole original fee. A policy deadline also limits these refunds. Someone who can’t come could move to your cheapest ticket just to get money back, even if you don’t give refunds. They would still hold that place. Saving a policy change on a published event tells ticket holders.

Attendance registration

In More options, open Checking people in to choose how Hubbaly counts attendance.

  • Scan tickets and check in by hand means attendees must be checked in to count as attended. Staff can use Scanner or Event Day.
  • Off means Hubbaly will not register attendance for this event. Use it when attendance records are not needed. Tickets are not marked as no-shows, and they show no QR code, because nothing at the door checks one.

An event without tickets always has check-in Off. If you add tickets later, or move it on from collecting interest, it starts with Scan tickets and check in by hand.

With Scan tickets and check in by hand, staff can choose Check in from the people list. This stays available in Attendance records after the event, with no time limit. The Scanner still closes 4 hours after the event ends. A ticket purchase alone never counts as attendance.

Event chat and images

  • Under More options, open Event chat. Create initial event chats creates useful event chats at the same time as the event. You can start with ticket-holder and staff chats, choose the membership behaviour for each chat, then adjust chat in Event Admin after creation.
  • Flyer or artwork is optional. Upload a clear square image if you already have one; otherwise you can add or replace event images after the event record exists.

Register interest events

Collect interest first events gather demand before the date, venue, or tickets are final. This section explains who gets emailed and when, and how to move the event to tickets without losing the interest list.

How people join the interest list

  • Logged-in people register instantly from the event page. They do not receive a confirmation email and count as active straight away.
  • Email-only visitors get a confirmation email first. Their registration stays pending until they click the confirmation link, which is valid for 7 days. Submitting the form again within 10 minutes does not send another email.
  • Registering interest never reserves a place or guarantees tickets, and it does not add the person to your hub. The interest list stays separate from tickets sold, the waitlist, attendance, and hub membership.
  • The confirmation email includes a manage link (valid for 180 days) so email-only registrants can cancel themselves later. Logged-in people register without one and cancel from the event page instead.

Reminders for a scheduled ticket sale

Once tickets have a sale time ahead, people who cannot buy or join a waiting list yet can choose Tell me when tickets go on sale on the event page. A visitor without an account confirms their address from the email first. Hubbaly reminds each person ten minutes before their own opening: earlier for someone in a group that buys first. Anyone with an account can also get an alert on their phone and in Hubbaly, according to their settings.

A reminder does not reserve a ticket or join anyone to your hub. It also adds the person to the same Interested people list for event news. Anyone already on that list must ask for the automatic reminder themselves. If you move the sale before the reminder goes out, the reminder follows the new time. A person is never reminded twice about the same sale. They can ask again when you set a time for a later release.

A signed-in person can choose Cancel reminder on the event page while the button is there. The alert email includes Manage or cancel event interest for everyone. In Event admin → Tickets, Interested people tells you when Hubbaly will send each alert and how many emails it could send. There is nothing to press while a reminder is waiting.

When interested people get emailed

Changing to tickets does not send anything by itself. The emails an interested person can receive:

  1. Confirmation email: sent immediately on sign-up, but only for email-only registrations (see above).
  2. Updates you compose: send one whenever you have news. Compose email update on the Interest tab and Ticket setup always opens Email Studio with the Registered interest audience preselected; only active registrations receive it, duplicates are removed, and unsubscribes are respected. Write an email on Communications preselects this audience only while the event is still collecting interest; after the move to tickets it defaults to ticket holders, so check the audience there before sending.
  3. Tickets-on-sale alert: Hubbaly sends it to people who asked for a reminder before a scheduled sale. If you open sales without setting a time, or Hubbaly could not send the reminder, Send tickets-on-sale alert is available on Tickets once tickets can be bought. People already told about that sale are left out of the manual alert.
  4. Event change notifications: when you save edits that affect attendees, the edit flow asks who to notify. You can choose ticket holders, interested people, hub members, or nobody.

Moving from interest to tickets

  1. Finalise the date, time, and venue, then update the event details.
  2. Open Edit event and switch the event setup to Tickets available now. The interest list and its history stay attached to the event.
  3. Create at least one ticket type on Ticket setup. For paid tickets, finish Stripe payment setup first.
  4. Set a sale time if you want people to be able to ask for a reminder. If you open sales without a set time, you can press Send tickets-on-sale alert on Tickets once they are buyable.

The alert only sends when the event is published, in tickets-available mode, has a valid start and end time, and has at least one active ticket type people can buy right now (sales window open, inventory remaining, paid setup complete). If something is missing, the page explains what to fix instead of sending.

The alert sends once per event. People who unsubscribed, opted out, or disabled these notifications are skipped. Afterwards Ticket setup shows when it was sent, who sent it, and how many people were reachable or skipped, so the whole team can see it is done.

Managing the interest list

  • The Interest tab in event admin shows the roster with active, pending, and cancelled counts. Managers see masked email addresses; owners and admins see full contact details and can use Export CSV.
  • Answers to interest questions from the Register interest form appear under Answers on the same tab once the registration is active.
  • Hub-level demand across events lives in Hub -> Admin -> Insights.

Post-event reports

Use Event -> Admin -> Reports after the event ends.

  • On the night is the organiser closeout view for attendance, arrival timing, staff turnout, incidents, and follow-up items.
  • Line-up picks shows how many people tapped a bell for each time: at doors, at its start, and how that grew. It never shows who. Picks made before counting began are not included.
  • Money is the event-only settlement view for gross sales, refunds, disputes, Hubbaly fee, Stripe processing, original organiser net, final organiser net, and reconciliation anomalies.
  • Use the drilldown links instead of exporting people-level attendance data from this workspace. Event Day, Staff, and Incidents stay the canonical detail pages.
  • Export finance spreadsheet stays finance-only and summary-led. It does not include the attendance roster or per-person check-in times.
  • Download PDF downloads a print-ready report in your hub’s look: the first page opens on a band in the hub’s colour with its logo and the event’s name, then At a glance, Sales and arrivals, On the night (including the names of staff who did not check in, and open and resolved incident numbers), Money, and After the night. It is made to hand to a sponsor as well as to keep.
  • The post-event email is a shorter combined summary. Use it as the inbox handoff, then open the reports workspace for full detail.
  • If the event had paid orders and payments are ready, the finance view can hand you into Stripe with Manage in Stripe. If setup still needs work, the finance view will point you to the right hub payments action instead.
  • The report opens with a Wrap up card: thank your attendees, share the photos, and quick rows for open incidents or returns when there are any.
  • Open Sales to see Sales so far. The line adds up tickets sold day by day. If you run the hub, choose earlier events to see their lines beside it. With at least three past events that were on sale at the same point, you can see your usual and, for a single-date event with a set number of places, a likely finish.
  • Reports shows the same line under Sales pace, next to the other ways to review the event. The PDF keeps its own sales and arrival charts.
  • Choose Compare with other events on Sales or Compare events from Hub admin Analytics to see ticket sales, ticket choices and arrivals side by side. Hub owners and admins also see Gross sales and Organiser net.
  • In Hub admin → Analytics, see live ticket sales, recent events, members and joining, and how people found the hub. Choose a period in Overview, Sales, Community or Reach. Community groups people by how often they came, using check-ins. Waiting list and returns shows all-time outcomes. On the event’s Sales page, people who run the event’s owning hub can see Who is buying and a First time mark beside a buyer’s first order with the hub.
  • Refunds are split by who or what issued them, with a list of every refund and its source, and a Waitlist and Returns section shows joined, invited, bought through the waitlist, invites expired, still waiting at close, and returned seats passed on to new holders. The same lines appear in the finance spreadsheet.
  • The overview shows check-ins as a percentage of tickets.
  • The entry section reports only what recorded evidence supports: a reconciling No recorded check-in breakdown (not a blocked-attendees guess), with document state frozen once the door window closes while late check-ins still count.

Sale story

Once 20 tickets have been bought, the event’s Sales page and its report show a Sale story card about how your sales went. The PDF prints the same story. Only people who can see the event’s sales see it; buyers never do.

  • The headline follows what happened. A sell-out in minutes gets a minute-by-minute chart with the busiest minute, how fast half the tickets went, and how soon the first ticket went. A sell-out over days gets its busiest hour, noting an update posted just before it. Steady sales get the share bought in the final week, the busiest day, and the time of day people buy.
  • Sold out appears only when every place was taken: either every ticket that sold reached its own limit, or the event’s own capacity was filled. Otherwise the card says how many tickets went and how fast.
  • All places taken appears instead of Sold out when the last place went to a complimentary ticket or an offer not yet accepted.
  • Places taken adds up what holds your places, for example 30 of 30: 22 sold, 3 complimentary, 5 offers not yet accepted.
  • Times are counted from when tickets went on sale. If tickets went on sale at different times, When tickets went on sale lists each time, what went on sale and how it sold, and the headline says which time it counts from.
  • Tickets lists each ticket with how many sold, how fast it sold out, when its sales were stopped, or when it goes on sale.
  • A rush means many people buying within minutes: at least 10 tickets from 5 different orders within 10 minutes. One group booking is not a rush.
  • Only tickets bought through checkout count. Complimentary tickets and staff passes are left out; refunded tickets still count, because they were bought at that moment.

Understanding your event finances

Every figure in your event and hub finance comes from the same money trail. Here is what each part means.

  • Gross sales: what buyers paid before anything is taken off.
  • Hubbaly fee and card processing: our platform fee and Stripe’s card fee. On Connect direct-charge events these come out of your payout; the finance breakdown always shows them.
  • Original organiser net: gross minus those fees, before any refunds.
  • Refunds: money returned to the original payer. A refund can come from three places, and each order’s detail page names which: a buyer’s return filled by a replacement buyer (automatic), a refund you issued yourself (manual, with the policy you chose), or one issued directly in Stripe.
  • Absorbed refund fees: when you fully refund under the cancellation policy you cover the fees that were already taken; this line is what that cost you.
  • Final organiser net: what you actually keep, which is original net minus refunds and lost disputes, plus any fee credits.

Refund policies and who pays the fees:

  • Standard policy returns the ticket price minus the fees already spent, so the buyer bears those fees.
  • Full cancellation returns the whole ticket price and you cover the fees, which then show as absorbed refund fees.
  • A return that resells settles only once a replacement buyer is found; the original buyer is refunded from that sale.

Payouts and a negative available balance:

  • Available balance can read negative for a short while when refunds went out before recent sales have settled. The pending amount arrives with your next payout and clears it. It is a timing gap, not a loss.

Data health:

  • The data health checks confirm every order’s payment records arrived from Stripe so your report is audit-grade. They do not affect your balance. If something needs attention, use Sync Stripe ledger from the finance view.

To see the full story of one order, with payment, fees, and every refund named by who and when, open it from the Orders list or the finance report and read its money timeline.

Hub finance

Use Hub Admin -> Finance for hub-wide money, payouts, refunds, disputes, and reconciliation. Hub owners and admins can open it. Managers see each event’s money in that event’s Reports, and get finance alerts about their events there.

  • Hub Finance is the hub-level view for orders, refunds, payout history, and open dispute tracking across events.
  • The summary highlights Gross sales, Final organiser net, Available balance, and Paid out totals; a secondary strip breaks out Platform fee, Card processing, Original organiser net, Refunded, and Open disputes.
  • Open disputes surface as an alert banner above the hero stats while any remain open, with amount, reason, evidence deadline, and event context where Hubbaly can map the dispute back to an event.
  • Open in Stripe takes you to your hub’s Payouts list in Stripe, where you can choose a payout for full details. Hubbaly still shows recorded payout history if the live Stripe read is temporarily unavailable.
  • Each event card expands to show Gross, Platform fee, Card processing, Original organiser net, Final organiser net, Refunded, and ticket-type revenue rows.
  • Use the Export CSV action in the page header for date-scoped finance CSVs, and use each event row for attendee export without exposing attendee email addresses.
  • Use Finance digest emails on the finance page to choose Off, Daily, Weekdays only, or Weekly (Monday at the chosen local time), set the local send time/timezone, and add finance recipients beyond the owner.
  • New hubs start with Weekly, covering the previous seven days. Existing saved choices stay as they are. Each email says Daily, Weekday or Weekly finance digest in its subject and heading, and shows the dates it covers.
  • Scheduled digests are suppressed automatically when the reporting window has no meaningful finance activity, so Hubbaly does not send zero-activity summary email.
  • Critical finance alerts stay immediate for payout failures, Stripe capability issues, disputes, and reconciliation problems even if scheduled digests are off.
  • Event admin Tickets stays focused on event setup and live operations.
  • Sales shows recent orders with their ticket types and View order for the full record. Use Orders for the full searchable list with ticket types, and Sold tickets for ticket holders, transfers and refunds.

Check Hub -> Admin -> Settings -> Payments before publishing or changing live paid tickets.

  • Fully ready means the hub can take payments and the platform checkout path is active for that hub.
  • Connected, rollout not active means the hub has a connected account, but this hub can still use legacy paid checkout until Connect rollout is active for it.
  • Platform setup incomplete or Needs review means do not treat paid-ticket setup as healthy yet. The hub may be connected, but the platform checkout path or recent sale evidence does not match the expected Connect route.
  • This is not determined by old event versus new event alone. Hub rollout policy and the checkout path used at sale time matter more.
  • If a newly sold paid ticket later shows 0 Hubbaly fee / 0 Stripe fee in Event Admin refunds, pause and review payments setup before more sales. That usually indicates legacy routing or incomplete platform paid-ticket readiness rather than a harmless display mismatch.
  • Draft events can still keep paid ticket types saved while setup is incomplete, but publishing or changing live paid tickets is blocked until the required readiness checks pass.

Event admin settings

Use Event -> Admin -> Settings to control the event rules before people arrive.

Event admin settings basic info

Set the event name, description, and date/time carefully.

  • Keep major date/time changes deliberate once tickets are live.
  • Add enough description for attendees and staff to understand the event quickly.
  • Treat this as the source of truth for what the event is and when it happens.

Event admin settings location

Use this to set the venue name and address the team should rely on.

  • Make sure the location is accurate before publishing.
  • Keep it consistent with any email or update copy you send later.

Event admin settings images

Use event images for the event page, admin context, and outbound communications.

  • Upload clear artwork that still makes sense on mobile.
  • Replace test artwork before the event is public.

Event admin settings visibility

This decides whether the event is hub-only, public, or private.

  • Hub members only keeps discovery and checkout inside the hub. A signed-in person who opens the link before joining a public hub is told the event is for its members and offered the next step: join, ask to join, or a note that their request is waiting. For a private hub the link says only “We can’t show you this event”.
  • Anyone allows direct-link viewing and public ticket access where policy allows.
  • Invited people only hides the event from everyone except invited people and authorised organisers. It never appears in discovery, lists, or search, and an uninvited visitor with the link sees “We can’t show you this event”. Invite people through the event’s invitations. Purchase invites cannot be used on a private event, because only an event invitation lets someone in. To sell a private ticket there, tick it in the invitation (see Private tickets on a private event).
  • Waitlists and ticket returns are not available on private events: sell-out recovery needs an open audience, so setup shows this as unavailable rather than offering switches that cannot work.
  • Public events with active tickets cannot be switched back to Hub members only until active ticket count returns to zero.
  • Review this alongside ticket eligibility so the public/private behaviour stays consistent.
  • Public event pages can show hub context, but they only link back to the hub overview when the hub itself is public.
  • Public event pages can reuse the hub banner only when the hub is public. Private hub banners are not reused on public event surfaces.

Public event pages, search, and sharing

Treat public event visibility and public ticket access as related but separate decisions.

  • Only Public events get a real public event page that you can share outside the hub.
  • Hub members only events do not have a public event page, so they are not intended for normal public discovery or search results.
  • An event can still have a public event page even if tickets are members-only. That page can explain the event publicly while keeping buying restricted to eligible members.
  • Appearing in search results is not immediate or guaranteed. The main requirement on your side is that the event actually has a public event page and clear public-facing details.
  • Use a stable event slug, a clear event title, and a short description that explains what the event is and why someone should care before they click through.

When someone shares a public event link, the preview usually comes from the event’s public metadata.

  • The social sharing card typically uses the event title, description, and a main image.
  • If an event flyer is available, that is usually the strongest image for the social sharing card. If not, Hubbaly can fall back to other event artwork.
  • Choose artwork that still reads well in a wide preview crop and does not rely on tiny edge text.
  • Review public event details before sharing widely, because the card preview often becomes the first impression people see in messages and social feeds.

Event admin settings tickets and access

Use this section to decide whether tickets are required and who can get them.

  • Turn ticketing on only when the event really needs controlled entry, reservations, checkout, or QR access.
  • Event-wide sales caps live in Event Admin -> Tickets, not here. Set one only when all ticket types should share a single sell-out limit.
  • Choose whether tickets are member-only, member-plus-guest, or public.
  • Members only: only hub members can buy, ticket 1 stays with the buyer, and every extra ticket must be assigned to an active hub member during checkout.
  • Members + guests: only hub members can start checkout, but extra tickets do not all need a designated member up front. Assign existing members during checkout if you already know them; any extra tickets you leave unassigned stay on the buyer account for now so you can reserve places for guests without naming them first.
  • Public: anyone can buy when the event is public-listed. This is the only mode that enables the separate guest-checkout flow for signed-out buyers.
  • On a public event you can keep one ticket for hub members: in the ticket’s Buyers step, under Who can buy it?, choose Hub members. Visitors then see the ticket’s name and price, marked Members only, with sign-in and join guidance. Hub members buy it from the normal event page.
  • To keep a hub members ticket out of sight as well, answer No under Can people who are not members see it? Only hub members see that ticket.
  • A hub members ticket on a public event is one per member. A member buying more than one keeps one and chooses a different hub member for each other one before checkout. Guests use a ticket that anyone can buy. A member who already holds one cannot be sent another, and an organiser cannot move one to them.
  • Paid ticket types can stay saved while the event is still in draft, but once the event is live Hubbaly requires both hub payment capability and platform paid-ticket readiness before paid sales continue.
  • An authorised organiser can open the buyer page before publishing and complete a real test purchase. The page clearly warns that paid tickets will be charged and all test tickets use real inventory and capacity. The draft event remains hidden from everyone who is not authorised to manage it.
  • Keep ticket type names short and recognisable. Hubbaly caps ticket type names at 100 characters so names fit admin feedback, checkout, emails, and payment-provider records.

Event admin settings optional features

Optional features in Edit event holds parts most events do without. Each one appears in Event admin’s menu only once the event uses it.

  • Event shop: choose Add Event shop to sell items or services connected to the event without making them tickets. Shop then appears in the menu. Adding a shop does not open sales. Until anything has sold, Remove takes the shop off the event again, as does Remove Event shop on the empty Shop page: items on sale come off sale, Shop leaves the menu, and everything you set up comes back if you add the shop again. Once anything has sold, the shop stays, so its orders stay within reach.

  • Partners: for an owner or admin of the hub, Open Partners shows every way to work on the event with other hubs and organisers, and each option says when to use it:

    • Co-host with another hub runs the event together with another hub, with your hub as the lead. It needs Who can view this event? set to Anyone, so both hubs’ members can see the event; on any other event the card says so and Change who can view opens that setting. You can still sell tickets to members only, under Tickets and access.
    • Be part of a bigger event is for when your event is one part of something bigger that another organiser runs, like one night of a festival.
    • Bring other events into this one is for when your event is the bigger one, like a festival, and other organisers run events that belong to it.
    • Hand this event over gives a draft you built to another hub, or to someone new to Hubbaly. Only a draft that has sold nothing can be handed over.

    Partners appears in the menu while a hub or event is invited or working with yours, and leaves when the last one ends.

Hosting an event with another hub

Two hubs can run one event together when anyone can view it. The hub that made the event stays the lead and invites the other from Partners, under Co-host with another hub: paste the other hub’s link (for example hubbaly.com/hubs/their-hub), check the hub that shows before Send invitation, and choose the event roles its owners, admins and managers can use. Roles that touch your money say so.

The invited hub’s owners and admins can open Hub admin, then Dashboard, and choose Review invitation while an invitation waits. This opens Hosting invitations, which is also in the Hub admin menu with the number waiting. A new invitation also appears in Alerts if you allow invitation alerts. Accept first shows what accepting means:

  • Who sells. The hub that made the event runs the sales. All ticket money goes to its payment account, and it handles refunds and payouts. Hubbaly does not split payments between hubs; if your hubs share money, arrange it between yourselves.
  • Both hubs. The event shows in both hubs’ events, and its page says it is hosted by the first hub with the second.
  • Members. Members of either hub can buy members tickets without joining the other hub. Any group prices the first hub sets are only for people in its own groups.
  • Updates. An update about the event can go to members of both hubs, or to either hub’s members. Someone in both is told once.
  • The door. With Manage event team, the other hub can add its own members, or anyone by email, as event staff who scan tickets and hand out Event shop orders. Both hubs see everyone on Staff, and each hub changes or removes only the people it added. Checking members and required ticket documents stays with the first hub. Anyone the other hub added stops when hosting together ends.
  • If it ends. Either hub can stop hosting together at any time. The event then leaves the second hub’s events and the second hub loses its event roles. Anyone who already has a ticket keeps it.

Once accepted, the second hub’s owners, admins and managers find the event under Hosting with other hubs in Hub admin, Events, and in Event admin their label says Hosting with the first hub. Both hubs’ owners and admins get an email when an invitation is accepted or declined and when hosting together ends, and the second hub’s organisers get one when their roles change.

Event resources (FAQ, notes, links, files)

Manage event-facing resources in Event Admin -> Edit event -> Event resources. This card covers practical details that do not belong in the main event description. Press Add and choose a kind, or press a resource to change it: each opens its own window, with the event page beside it showing the resource in its place as you type, and saves on its own.

Good examples:

  • Arrival time, parking, transit, and meeting-point notes.
  • Accessibility details and what to bring.
  • Private joining instructions for ticket holders.
  • Short FAQs such as “Can I bring a guest?” or “What happens if it rains?”
  • Downloadable PDFs/images such as floor plans, schedules, and waiver readables.
  • External links to maps, partner pages, or supporting docs.

Each resource has its own visibility:

  • Everyone: visible to anyone who can view the event page.
  • Ticket holders: visible only to people with an active ticket for this event.
  • Members and ticket holders: an older choice, kept until you change it, visible to hub members and active ticket holders.

File limits: PDF, JPEG, PNG, WebP, GIF up to 25 MB. Downloads are access-checked: a denied download returns 404 (privacy boundary) instead of revealing that a private file exists.

Attendee documents/waivers and post-event feedback forms live in their own tabs in Event Admin -> Forms and documents.

Event admin settings age restriction

An age restriction tells people who the event is for before they buy. It is your rule for the door: Hubbaly does not ask anyone their age and checks nothing.

  • Turn on This event has an age restriction in Access and attendance on Edit event. It starts at 18+. Choose 14+, 16+, 18+ or 21+, or Another age for an age and over or a range such as 11 to 16.
  • Add an explanation if you like, such as Photo ID checked at the door by the venue.
  • People see it on the event page, at checkout before they pay, on their ticket and in their ticket email.
  • When your hub has an age restriction, your events follow it. Use Change for this event to give one event a different restriction, or none.
  • Checking ages at the door is up to you or the venue.
  • An album for an event restricted to 18 or over starts as Ticket holders. You can change it.

Event admin settings attendance registration

This controls how Hubbaly registers attendance for the event.

  • Scan tickets and check in by hand lets staff use Scanner or Check in on Event Day.
  • Off keeps the roster read-only, does not mark tickets as no-shows, and shows no QR code on its tickets.
  • An event without tickets always has check-in Off.
  • After the event, Attendance records still lets staff check people in. The Scanner closes 4 hours after the end.
  • Keep the attendee list visible only if that suits the event privacy posture.
  • Ticket QR visibility is platform-managed. Hubbaly shows attendee QR codes 24 hours before the event starts, and there is no per-event timing setting in v1. With check-in Off, tickets show the event itself instead: its picture, or the hub’s colour, with the date and No check-in at the door.

Event admin settings personal statuses

Personal event statuses let attendees say what they are hoping to get out of an event, with a short note and an optional photo. It is a flexible way to signal intentions and interests ahead of the day, for example:

  • Key interests or topics to explore at a meetup or conference.
  • Whether you are open to chatting and meeting new people.
  • What you are looking for on the night, such as dancing buddies at a club night.

How it works:

  • Statuses are private to the event. Only fellow attendees, the event host, and hub admins can see them; they are never shown publicly.
  • Turn Personal event statuses on or off in the Attendance registration section of Event -> Admin -> Settings. Hubs choose whether the feature is on by default for new events.
  • Attendees add or edit their own status from the event’s attendees page, where it appears alongside the guest list, and it keeps working even when the attendee list is hidden.
  • Organisers can clear an attendee’s status if needed; clearing removes it for everyone.

Event admin settings chat

This section is informational only. Event chat uses separate chats.

  • Use Event -> Admin -> Chat to manage the actual event chats: create chats, rename them, disable them, and restore them later if needed.
  • /chat can also create an event chat now. Start from the main chat page, choose Event chat, then pick the event you manage.
  • If an event has no active event chats, the event page simply does not show event chat until an organiser creates the first one.
  • Ticket holders gives access to anyone with an active ticket for the event, including people using the same Hubbaly account to hold a ticket without being hub members.
  • Ticket holders who are members is useful when the event is public but the chat should stay inside the hub membership boundary.
  • Staff is for event staff coordination.
  • Checked-in attendees is a later/additional chat option for post-attendance discussion. It only becomes relevant once people are checked in, either by scanning a ticket or by marking someone attended manually.
  • Name the chat for the job people will recognise, then let the audience preset control who can get in.
  • Use event updates for organiser announcements. Event chat no longer includes a separate event announcements chat.
  • Use Event -> Admin -> Forms and documents to manage required forms.

Event admin actions and danger zone

These are operator-only actions with wider impact.

  • Choose Duplicate in Hub admin -> Events (inside More on a phone) or at the top of Edit event. The usual Create event page also offers Duplicate an event when there is an earlier event you can use.
  • Name the new event, choose its start and leave out any dates, tickets, forms, guide, line-up, pictures, discount codes or shop items you do not want. Discounts go off with Tickets and come back on with it. A bundle stays behind if a ticket it needs is left out. London clock times stay the same across a clock change; sales phases, sale windows, delivery dates and the refund cut-off move with the start. A year later means 52 weeks, keeping the weekday. After Done, the date and time you chose stay in view. An original without a date makes an undated copy. An event without tickets keeps the days you choose.
  • Create draft opens the copy’s Edit event, with a short list of what to check before publishing. Its link comes from the name you chose. The team starts empty. Nothing is sent while you make the draft.
  • While the copy is a draft, Ask 1 staff member from the last event or Ask 3 staff from the last event (with the number who can be asked) opens Ask last time’s team again in Staff: the people who helped last time, with their roles and the copy’s dates they did before, all ticked. Untick anyone you don’t want, then send. Each person gets the same invitation as one sent by hand. Anyone whose dates were all left out, whose role is archived, who has left the hub or who is already on the team is shown with the reason and is not sent anything.
  • The guide keeps its notes, FAQs, files, plans and places. Line-up acts keep their day and time, with left-out days removed. Feedback forms start as drafts without answers. Shared discount codes start with no uses and keep their pauses and disabled codes. Copied one-use lists start empty. Open Discounts and choose Create discount on the copied event to make fresh one-use codes.
  • Shop items start as drafts, with counted stock at 0 and unlimited stock still unlimited. The shop stays closed. In Edit event, choose Add Event shop under Optional features, then check the copied items, add stock, confirm selling details and choose when to sell. The copy has its own Shop QR.
  • Owners, admins and managers can duplicate. A groups-first original needs an owner or admin. Its copy starts privately for the same groups that still exist and keeps how it opens to the whole hub. A moved opening date that has passed is left empty for you to choose; if every group has been archived, the copy is an ordinary hub event. Buyers, orders, money, check-ins, messages, updates, invitations and photos never copy.
  • If the ticket setup cannot be copied, nothing is made and your choices stay in the sheet. Choose Leave tickets out to copy the rest, or open the original’s ticket schedule. A problem with the dates must be fixed in the original first.
  • Delete/archive actions should only be used when you are sure the event should no longer exist in its current state.
  • Pause before any destructive change once staff, tickets, or attendees exist.

Ticket lifecycle (attendee)

  1. Discover an event.
  2. Select ticket type and quantity.
  3. Complete checkout (or free/comp flow).
  4. Open ticket in My tickets or from the secure hosted ticket link sent by email.
  5. Complete required forms before arrival.
  6. Present QR at check-in.

Additional ticket access notes:

  • Signed-in ticket holders use My tickets and the ticket detail page as the main source of truth, including the ticket links sent in purchase confirmations and reminder emails.
  • Placeholder or email-only ticket holders can use the secure hosted ticket link sent in purchase confirmations and reminder emails.
  • The scannable QR appears 24 hours before the event starts. Before that, ticket surfaces show the readiness state/countdown instead of the QR itself.
  • If the event’s check-in is Off, the ticket never shows a QR code. In its place it shows the event: the event’s own picture, or the hub’s colour, with the day, date and times and No check-in at the door. The copy saved for no signal shows the hub’s colour. The ticket is still your booking.
  • If required forms are still incomplete, the ticket surface sends the holder into the guest-consent flow and then returns them to the ticket afterward.
  • If you lose a guest/email ticket message, use Find my ticket. Recovery emails send signed-in holders back to My tickets and send email-only holders fresh hosted ticket links for upcoming active events.
  • If a hosted ticket link has expired or no longer works, use Find my ticket to request a fresh access email.
  • Hosted guest-ticket surfaces offer Set up my account. Hubbaly first emails a secure link to confirm the address, then asks for a username and password once. Finishing setup keeps the ticket and makes it available in My tickets.

Changing someone’s ticket

If you can Manage event sales, open the event’s Admin → Sales → Sold tickets page and choose Change beside an active ticket. Pick another ticket type, session, or both, check the message and choose Change ticket. The choices show today’s prices and places left; a full choice stays unavailable until there is room.

The holder pays nothing when you move them to a pricier ticket. On a cheaper move, Refund the difference starts unticked. Tick it to offer a refund, then check or edit the amount, up to the money left. The change stays saved if the refund needs another attempt. Their original order and amount paid stay as they were, and the latest change appears below their ticket’s actions.

They keep the same reference and QR code, so a saved or printed copy still works. Only the holder gets the change email, with the new details and a new calendar file when the event has a date. A guest can open their private ticket link without making an account.

If the person bought Event Extras for the old session, the reminder tells you those items stay as they are. Change or refund them separately from Shop orders if needed.

You can change tickets while the event is published and has not ended. Staff passes, tickets bought as part of a bundle, tickets already checked in, and tickets with a transfer or refund under way cannot be changed. A complimentary ticket stays complimentary. The new place must fit within the ticket’s overall limit and the room limit; an organiser’s free move does not use a sales phase’s places.

Offline access and installing the app

Hubbaly keeps working at the door even when the venue signal drops, as long as you open things before you lose connection.

  • Once a page such as My tickets or a ticket has loaded while online, it keeps showing the last saved copy offline, with a saved X ago note, instead of an error. A brand-new page load still needs a connection, so open your ticket before you reach the entrance rather than in the queue.
  • The scannable QR appears within 24 hours of the event. Load the ticket once inside that window and it stays presentable offline.
  • You can install Hubbaly to your home screen from your browser (Install app / Add to Home Screen, or the in-app prompt when it appears) for faster, more reliable access on the day. The installed app is the same Hubbaly, not a separate app-store download.

Guest checkout

Use guest checkout when a public event allows account-free purchase.

  • Guest checkout only appears on published public-listed events with Public ticket access. Members only ticket types still require a signed-in eligible member.
  • The guest form is email-first. Buyers enter an email address and can optionally add a name before selecting quantities.
  • If that email already belongs to a real Hubbaly account, guest checkout is blocked on purpose. Sign in with that email instead so the tickets attach to the existing account.
  • If you already have or want a Hubbaly account, use the Sign in or Create account links on the guest-checkout page before paying. Hubbaly keeps your email and selected ticket quantities when it hands you into auth.
  • Free guest checkout confirms immediately on the page and by email.
  • Paid guest checkout goes through Stripe, then returns to a guest-friendly processing screen that verifies the payment and hands off to ticket access without assuming you are signed in.
  • If you close or cancel out of Stripe before paying, Hubbaly returns you to guest checkout with your current guest details and ticket selections preserved.
  • Guest purchasers are sent a secure hosted ticket link in purchase confirmations and reminder emails. Hubbaly does not send the raw scannable QR directly in the email body.
  • The hosted ticket page is read-only. It shows ticket details, readiness state, required-form status, and then the QR itself once the 24-hour activation window opens.
  • If required forms are still outstanding, the hosted ticket page sends the holder into the guest-consent flow and then safely returns them to the same ticket page afterward.
  • Find my ticket appears only on guest-relevant surfaces: auth pages, guest success / hosted ticket flows, and public event pages where guest checkout is actually available.
  • Recovery is email-only and privacy-preserving. Hubbaly always shows the same success state, then emails either My tickets or secure hosted ticket links for upcoming active events tied to that email.
  • Guest holders can turn their ticket email into a full account from the hosted ticket page or guest-completion flows. Select Set up my account, open the secure email link, then choose a username and password once. Paid and free checkout setup continues to My tickets; hosted-ticket and form flows return to the same ticket and keep the hub context.
  • About 24 hours before the event, guest/email-only holders get one state-aware reminder email: either the QR is ready, or required forms still need to be completed before the QR becomes available. At events with check-in Off only the forms reminder is sent, and it does not mention a QR code.
  • Creating an account later with the same email upgrades the placeholder guest account and keeps those tickets/purchases attached to the new real account automatically.

Public event albums

  • Public event pages can show event-linked public albums.
  • Album cards open the specific album directly.
  • The broader View all public albums handoff is only shown when the hub itself is public.

Ticket types

Ticket types let you shape how people book:

  • Create different offers such as General Admission, VIP, free entry, guest list, or staff tickets.
  • Choose the price, whether this ticket needs its own smaller limit, and who can buy it.
  • Ticket prices can be free, or at least £1.00 for paid entry.
  • Choose Hub members under Who can buy it? when a ticket on a public event should only be available to hub members. On an event that already sells to hub members, every ticket is.
  • Use a sales window if you want sales to start later or stop before the event begins.
  • Turn a ticket type off by making it inactive instead of deleting it when you want to pause sales.

The Sales step keeps the capacity, ticket total, price, availability, and later sales phases in one place.

Event capacity or a ticket’s own limit?

Use Event admin → Tickets → Rules → Ticket schedule and capacity to set how many people can attend. Use a ticket’s Sales step for its own limit, price and sales phases.

Tickets per buyer is a different limit: it controls how many tickets one account can buy across orders, not how many places are available. See Buyer limits.

Sales phases let the same ticket change price or release more tickets later. Each has a start date; a phase with a fixed number of tickets can also let the next one open early after those tickets sell. A later phase does not necessarily start as soon as the earlier one sells out. See Sales phases for the setup and what buyers see.

Two numbers control how many tickets sell, and they answer different questions:

  • Shared capacity answers “how many people fit?”. Every attendee ticket draws from it. A one-time event has one event capacity. An event with several dates or times has one capacity for each date or time, because people attend a particular one. Set it in Rules → Ticket schedule and capacity on the Tickets page, or review and change it at the top of the ticket’s Sales step.
  • A ticket’s own limit answers “how many of this kind will I sell?”. Set it with Limit this ticket to. It is an extra, smaller ceiling: the ticket still draws on the shared capacity.

When to use which:

  • A real venue? Always set the shared capacity. It is the only number that stops your ticket limits adding up past the room. Two tickets capped at 200 each can otherwise sell 400 into a 350-place venue.
  • Several ticket types sharing one room (Adult, Child, Concession): let them share that capacity rather than guessing a split. A wrong split strands seats, showing Sold out on one ticket while places sit unsold on another. Sharing lets the mix float, so the first 350 people get in whatever tickets they hold.
  • Several ticket types across repeated bookable times (Low, High, Adult, Child): create each ticket once with Every bookable time. Buyers still choose one exact time, and every paid, free, complimentary, returned, or waitlist ticket uses that time’s physical capacity. The ticket’s optional own limit is one product total across all times; it never replaces or adds together the per-time capacities.
  • Bundles work best over shared capacity: a family bundle just needs 4 places in the pool, rather than stock left in two separate allocations at once.
  • Add a ticket’s own limit only for something genuinely scarcer than the room: 20 VIP seats, 30 workshop places, 50 dinner add-ons, or a deliberately limited offer such as 100 early-bird tickets.
  • Both together is the usual happy setup: shared capacity as the safety net, own limits only on the scarce tiers, everything else unlimited and drawing on the shared places. Selling always stops at the tightest number that applies.
  • A multi-day pass uses one place on every date it covers, so each of those dates needs its own capacity. There is no single number across dates, and adding those capacities together is not a headcount.
  • Leaving capacity blank is a valid answer when the event or date has no fixed maximum. For a pass, clear the optional common capacity field to leave its unlimited dates as they are. Removing a capacity you already set is a separate, explicit No fixed capacity choice; clearing the box on its own just asks for a number.

Things worth knowing:

  • A new ordinary exact-time ticket limit has to be lower than the shared capacity it draws on, because a limit at or above it could never be the number that stops that one line. Sales phases with their own ticket numbers may add up to the shared capacity exactly, because the phase numbers decide how every place is released; they still cannot add up to more than the shared capacity. An Every bookable time ticket is the other explicit exception: its one product limit is shared across all current and future times, so it may be larger than one time’s physical capacity. Beside the quantity, Hubbaly confirms that this is one overall ticket limit and repeats that each time still keeps its own shared physical capacity. If you already had an exact-time ticket limit and later lowered shared capacity, your value is kept and the Sales step explains when it is not currently the tightest limit.
  • Sales phases with per-phase ticket numbers currently need the ticket’s own limit. A ticket sharing capacity can still use phases, but they change price on set dates rather than selling out in batches. If you want 100 early-bird tickets in a 350-place venue, give that ticket its own limit of 100.
  • Limits are ceilings, not reservations. Sharing the capacity does not hold places back for any one ticket type.

Ticket schedule: dates, times and ticket coverage

Hubbaly keeps three ideas separate so a retreat, theatre run, weekly course and festival can all use the same truthful model:

  1. The overall event span is the earliest start and latest end shown in event headers and lists.
  2. Dates or times are explicit attendance windows used when access, capacity, price, check-in, staffing or reporting differs within the event.
  3. Ticket coverage says which of those windows each ticket type admits.

Words such as festival, course or showing are examples, not stored event types. One event can legitimately sell a whole-event pass, a fixed weekend pass and separate day tickets together.

Set up the dates and times

A new ticketed event starts with one start and end. Select Add more dates or times when people need several attendance windows, then choose an Event format:

  • One event across several days: People can attend on one or more days. You can offer day tickets and multi-day passes.
  • People book a specific date or time: Each show, class, tour or appointment is booked separately and can have its own tickets and capacity.
  • Keep the start and end already entered closes the window and keeps one continuous event. In Tickets the same choice is called One continuous event.

For a multi-day event, start with Consecutive days, Repeating days, or Add dates myself. For separately booked dates and times, use Create bookable times, Create a repeating schedule, or Add times myself. Once you choose, the three options fold to one line that says which one you chose; Change brings them back.

When you add dates or times yourself, each one is its own form with a start and an end, and the one you are adding is always open. For a multi-day event they are named Day 1, Day 2 and so on. The first one starts with the event’s existing start and end when they are available. Until you choose a schedule method or edit its rows, changing or clearing the inline dates, times, or capacity also updates those starting values; simply opening and closing the helper does not create a separate schedule.

Finish the entry you are on before the next empty one appears. The end follows the start until you set the end yourself. An empty day offers the next day with the same hours in one press, and nothing is filled in until you press it. Add another day opens the new day and folds the finished ones to one line each; Edit opens any of them again.

Beside the Review button the helper says how many are set, for example 1 of 2 days set, with a link to the one that is still missing. Review becomes available once every entry has a start and an end, with at least two for a new schedule, and trying to create the event with an unfinished entry returns you to this Dates step. The review lists what you typed in date order. If the finished entries use different hours, an optional Use these times for the others shortcut appears below them; it copies only the first entry’s start and end times and keeps the date each entry starts unchanged.

The bookable-times helper asks for First time, Duration in minutes, Break between times in minutes, Number of times, and Maximum bookings at each time. In Tickets, its date starts with the event’s existing Europe/London date. Capacity must be chosen deliberately before Preview schedule. Generated times may continue onto the next date automatically, so 36 five-minute times from 21:20 finish at 00:20 the next day. The repeating-schedule helper starts with one blank named-time row; examples such as Matinee and Evening appear only as placeholders. Every helper produces real editable dates and times, not a saved recurrence rule.

  • All controls use Europe/London time. A spring clock-gap time must be changed, and an autumn repeated-hour time asks whether you mean the earlier or later occurrence.
  • Manual row editing uses the same full date-and-time picker as a single event and always shows both dates so an overnight time remains deliberate. Its controls meet the mobile touch-target baseline, it identifies itself to assistive technology, returns keyboard focus after closing, and keeps unresolved clock-change warnings visible through Review and reopen. Once an occurrence is chosen, that choice and the correct London timezone also persist. The 30-minute controls move from the exact occurrence chosen, so crossing the repeated hour cannot silently add or subtract an extra hour.
  • Exact duplicate start/end windows block saving. Overlaps show a warning but remain allowed because two legitimate sessions may run at once.
  • Initial separate setup needs at least two rows. An existing schedule may later have one row left.

In Event Admin -> Tickets -> Ticket schedule and capacity, each date or time shows how many places are taken, with Full when every place is taken. Edit its label, time, or capacity there. The capacity box says what it cannot go below, the places already taken, and it can be emptied while you type a new number. Use Remove limit when a date or time has no physical maximum: an emptied box is not saved as no limit, and Save changes stops at that box until you type a number or choose Remove limit. With two or more dates or times, Set one capacity for several times opens its own panel: choose Set a maximum with Maximum people, or No limit, then tick the times under Apply to. The ticked times immediately preview what will happen and the fixed Save changes action appears. There is no separate Apply step, and nothing is saved until you choose Save changes. Unticked times stay unchanged. A date or time that cannot be removed says why in one line; one that can shows Remove this time. If all separate dates are removed, the same editor asks for the resulting single event’s capacity before save. Named repeating and bookable schedules do not offer a bulk usual-hours action that could flatten their different times.

How can people attend this event? opens on what the event is now. An event with no dates is One continuous event, with its own start and end under it and its places below, even if it was made before Hubbaly recorded this choice, and there is nothing to save. An event that has dates but no recorded choice asks you to Choose how people attend these dates. The warning that the event has one overall ticket limit as well as separate dates or times appears only when the saved event really has both.

When an event with no dates gets One event across several days or People book a specific date or time, the card first says what happens to its places: each new day or time starts with the event’s places, and the event-wide limit goes when you save. Then it shows two steps:

  1. Add the days (or times). Add days or Add times opens the window straight at how to add them, in two steps, without asking the format again. You need at least two: Save changes with fewer says Add at least two days before saving.
  2. What your tickets become. Each unsold ticket for the whole event on a draft event gets a plain choice. For several days: A pass for every day (chosen to start with), or A ticket for one day with the day. For bookable times: On sale at every time (chosen to start with), where the ticket’s own limit counts across all the times, or For one time only with the time. A pass made this way covers the days saved with it; a day added later is not added to it. A ticket with sales, or any ticket on a published event, cannot be changed this way.

On an event that already has days or times, Add days or Add times also opens the window straight at how to add them, without asking the format again, and one new day or time is enough.

A repeated schedule may also use one Limit bookings across selected times, such as allowing each buyer to book only one photography time. The choice appears once there are two times. A new limit starts with no times selected, and a time added later remains excluded until deliberately selected. On a published event, Save changes asks who to tell only when the change moves a date or time people have tickets for, or moves the event’s first or last time. A new capacity, label or booking limit saves with no question. The question is the same window Edit event uses, and it says what changed and how many people are booked. When a booked time moved, the first choice tells only the people booked on it; you can also notify all ticket holders, hub members, people who registered interest when the event collected interest, or choose Don’t notify. An invite-only event offers only ticket holders. The saved message says who will be told.

If a ticket is created while you are editing but the saved dates did not change, Hubbaly keeps your local rows and asks only for the new decision it needs. A whole-event ticket made while you first add days or times gets the same plain choice as the step above. On an event that already has dates, an eligible unused whole-event ticket on a draft event can be kept for one chosen time: choose Keep this ticket for one time, select the time and save the schedule. You can keep that exact-time ticket or create a new shared ticket for Every bookable time. A ticket with sales, holds, queues, invitations, returns, other protected history, or an incompatible setup remains blocked. If the saved schedule itself changed, your work stays on screen and only Discard my changes and reload the saved schedule replaces it.

Use one ticket setup across every bookable time

On a repeated performance or appointment schedule, the ticket wizard asks Which times can this ticket be used for?

  • Every bookable time is recommended when the same Low, High, Adult, Child, or similar offer should appear at every time. Create and edit that ticket once. Current times and times added later include it automatically.
  • One specific time keeps the established exact-time model for an offer that genuinely belongs only to one showing or appointment.
  • The wizard lists the covered times as read-only context. Physical capacity is edited in the schedule, not duplicated in each ticket. The shared ticket may have one smaller product limit across all its times, and Review explains when that limit is not the tightest one.
  • Waitlist and Ticket Returns start selected and marked Recommended for a fresh eligible ticket. A free ticket gives the place back immediately with no refund step; a paid ticket waits for a replacement sale before its refund. You can turn returns off where they are available.
  • Bundles do not include shared bookable-time tickets. Use ordinary exact-time tickets for a bundle whose contents must be fixed in advance.

What happens to people who already bought a ticket:

  • A ticket type still set to Whole event would admit every scheduled entry, so Hubbaly does not add a date or time while one remains. When an event first gets days or times, an unsold whole-event ticket on a draft event becomes a pass, an every-time ticket, or a ticket for one day or time, as chosen in the schedule. Any other whole-event ticket has to be reviewed in Tickets first. Adding entries never takes anything away from current holders.
  • A purchased shared-time ticket is tied to the exact time the buyer chose. Older Attendee chooses one tickets and fixed Selected parts passes keep their established admission rules.
  • Once a ticket type has any activity (a sale, a checkout reservation, a purchase invite, a waitlist entry or a ticket-return offer), its admission mode cannot change and its entries cannot be narrowed. To sell a different admission model after sales have started, create a new ticket type instead.

Per-entry pricing and admission:

  • New repeated-time setup uses Every bookable time or One specific time as described above. Existing legacy ticket types may still show Whole event, Attendee chooses one, or Selected parts and remain readable without being silently converted.

How buyers choose

  • On a repeated bookable-time event, the buyer opens one exact time first, then chooses among the shared and exact-time tickets available there. The same shared ticket can appear under every current time, but checkout records only the time the buyer selected.
  • Whole-event and fixed-pass tickets state what they cover and need no buyer time control. Older attendee-choice tickets keep their established in-card date selector.
  • A ticket on sale at every bookable time can go into the same basket for two different times. Add it from each time; each gets its own line and quantity.
  • Choices survive supported sign-in, hub joining, terms, waitlist, returned-seat and browser Back journeys. If a date ended or became unavailable while the buyer was away, Hubbaly removes it, explains what changed and asks for a current choice. Checkout still performs the final server-side validation.
  • Ended dates remain visible in coverage but cannot be newly selected. Sold-out dates can be selected only when the buyer can join that date’s waitlist or has a held/returned place. Low-stock and held-place messages appear on the relevant date.

Removing an entry, and going back to one event:

  • You can remove an entry while only Whole event tickets cover it and it has no activity of its own.
  • An entry cannot be removed once tickets are tied to it or it carries attendance history. Refund or move those first.
  • The final remaining entry has no separate remove action. To return to one continuous event, choose One continuous event. An existing multi-day pass with protected activity blocks that change. An eligible inactive, history-free pass must be deliberately deleted or kept as an inactive ticket in the same reviewed save.
  • A schedule can legitimately keep a single remaining entry (for example after removing an unsold showing). It stays a schedule and is not silently turned back into a single-date event.

If you need to cancel a date or time: there is no Cancel date action, and the capacity cannot be set to zero. Use Remove this time if the schedule allows it. If you cannot remove it, turn off the tickets sold only for that time to stop new sales of those tickets. Turning off a ticket sold at every time takes it off sale for all its times. Contact anyone already booked to arrange a move or refund, and deal with any open waitlist or ticket-return offers separately.

Derived dates: while a schedule exists, the event’s start and end come from the earliest entry start and latest entry end. Event Admin -> Settings shows that range read-only and links back here; edit the schedule entries to change the dates.

On a published event: Hubbaly asks who to tell before saving if a time someone has booked moves, or the event’s own start or end moves.

How dates show for buyers and holders:

  • Event lists, Home, Discover and the event page show the event’s dates together. Where the event page shows dates as buttons, choose one to jump to its tickets. A date shown as plain text is there for reference.
  • The event’s calendar download adds one calendar entry per scheduled date, not a single block spanning the whole run.
  • Confirmation-email calendar links match what was bought: the chosen entry for Attendee chooses one, the covered days for Selected parts, the first upcoming date for a whole-event ticket.
  • Reminder, purchase-invite, confirmation, and announcement emails name the dates for what each person holds. When a date cannot be stated with confidence, the email leaves it out rather than guessing.

Purchase invites (invite-only tickets)

Use an invite-only ticket type when a ticket should only be buyable through a private link you send, not listed on the public or member ticket page.

Making a ticket type invite-only

  • In the ticket form, under Where is it sold?, choose Private invite only. Invite-only types are hidden from the public and member ticket lists, from guest checkout info, and from search; only someone with a valid invite can buy.
  • The event’s normal rules still apply to invited buyers: membership (for members-only events), the sales window, and the sales cap. An invite never lets someone past a sold-out or closed sale.

Sending an invite

  • From Event Admin -> Tickets, open the invite-only ticket type and choose Invite.
  • Add one or more recipient email addresses, a default and maximum quantity per person, an optional expiry date, and an optional message.
  • Each recipient gets a private purchase link by email. Recipients who already have a Hubbaly account also get an in-app alert.
  • A recipient can never take more than the invite’s maximum.

Invites for events with multiple times

  • Whole event, or Selected parts (a pass): the invite works with no extra choice. The link admits the recipient to the entries the ticket covers.
  • Attendee chooses one (one entry): when you send the invite you also pick which entry it is for. The invite is locked to that entry and its price, so the recipient is not asked to choose a different one. The entry is shown on the invite email, on the recipient’s page, and in your invite list.

How recipients buy

  • Public events with guest checkout on: a signed-out recipient can buy as a guest with the invited email address.
  • Members-only events: the recipient is asked to sign in or join first; after signing in as an eligible member the purchase works.
  • On an open hub, a signed-in non-member can join the hub and buy in one step from the invite page.
  • If the invite link includes a discount code, the new total appears when the buyer chooses their tickets. For a separate code, open Have a discount code? in the Before payment summary and choose Apply. A discount for all ticket types covers invite-only tickets as well as listed ones.

Private tickets on a private event

  • Purchase invites cannot be used on a private event, so there the ticket’s Invite button opens Invitations instead. That page sits directly under Tickets in the event admin menu.
  • To sell a private ticket, tick it in the emailed invitation or the invitation link. The invited person sees exactly the tickets that invitation covers.
  • All active ticket types covers every ticket except private ones. When the event has private tickets, the form names them and offers Also include for each one. Once you add one, the invitation covers the tickets the event has at that moment; tickets you add later are not included.
  • Only the tickets you choose covers exactly the tickets you tick, private ones included.
  • The event page never lists private tickets.
  • On a private event, a ticket’s Where is it sold? choices read All invitations and Private invite only, and the ticket’s details show the same under Offer. With All invitations chosen, the On sale box sits under Sale status: untick it to take the ticket out of every invitation, even one that ticks it.
  • Someone signed in who buys through an invitation is offered to join your hub at checkout, as on public events: an open hub adds them straight away, a hub that approves members sends you a request, and an invite-only hub offers nothing.
  • Each invitation sets how many tickets one person can get in one checkout: Tickets per recipient for an emailed invitation, and Maximum per booking for an invitation link. Checkout stops there and says so, so set it to what each guest may buy. The event’s own per-person limit still applies.
  • To give an invitation link more places or more time, press Edit on it, then raise Total places or move Expires (UK time) later. The link itself stays the same, so people who already have it can keep using it, and a link that is fully used or has expired works again. Places cannot be lowered and the expiry cannot be moved earlier. A revoked link cannot be edited; Replace gives it a new address instead.

Managing invites

  • The invite list shows each invite’s status (active, used, revoked, or expired) and the bound entry for an “Attendee chooses one” invite.
  • Resend an unused invite, or Revoke one to disable its link. You can also bulk resend or revoke the active invites.
  • If a ticket type counts towards the event sales cap and the event is already full, you are warned before sending, because invited buyers would still be blocked by the cap until it frees up.

Sales phases

Use sales phases when one ticket type should release tickets and change price in planned stages without cloning separate ticket tiers.

  • Set a ticket’s own total in Sales only when this ticket needs a smaller limit than the shared event or time capacity. With one sales phase, enter that amount under Total tickets.
  • The Sales step starts with one price and availability setup. Choose Add a later sales phase only when the price or number released should change later; there is no up-front one-versus-several choice.
  • For a ticket with its own total, Add Phase 2 (and each later phase) asks: What should happen to the ticket total? Choose Keep the total at its current amount to move tickets from the preceding phase, or Increase the ticket total to create more tickets. Neither answer starts selected. The preview shows every affected phase and the resulting total before you confirm.
  • A ticket using only shared event or event-time capacity has no separate ticket total, so Add a later sales phase creates a dated price phase directly without a quantity question.
  • When phases are enabled, Phase 1 is the first live price for that ticket type.
  • There is no separate base price running before Phase 1.
  • If Phase 1 starts in the future, that ticket type shows as coming soon instead of selling at a fallback price.
  • For a ticket type with a finite overall limit, each phase releases its configured number of primary tickets. Once there are several phases, Sales shows one calculated ticket total instead of a second editable total.
  • Removing a clean future phase asks whether its tickets should return to the preceding phase or reduce the total. Combine remaining phases keeps the total unchanged. Finished sales history and promised tickets are never silently changed, and unsafe options are unavailable.
  • A phase can allow the next phase to open early after all released tickets have completed purchase. Checkout and waitlist holds do not count as completed purchases.
  • During a busy opening, Hubbaly checks the phase again while securing each basket. If Phase 1 has just sold out, the next phase opens and checkout continues automatically when the total is unchanged or lower.
  • If the next phase makes the basket more expensive, Hubbaly shows the old and new totals and asks before continuing. Cancelling keeps the buyer’s quantities, dates, identity, terms, and form answers in place.
  • While another checkout is completing the phase change, Hubbaly checks availability for up to 30 seconds. The buyer can check again without submitting or paying twice.
  • For an unlimited ticket type, sales phases remain scheduled price-only steps. They do not allocate tickets or open early on sell-out.
  • Each phase can be free, or at least £1.00.
  • Each later phase must start after the previous one.
  • Each later phase must cost more than the phase before it.
  • On a draft public event, the default start reads When the event is published; on an already published public event it reads Immediately. A set date still waits for the event to be published and the ticket to be active, and invite-only tickets remain limited to invited buyers. Choose a date only when this ticket should open later.
  • With sales phases on, the phases own the start of sales, so the ticket keeps only its optional end setting. Set an end if you want selling to stop before the event; Phase 1’s start is when selling begins.
  • Use clear phase names such as Early Bird, Standard, or Final Release so buyers understand what changes next.
  • Turning on allocated sales phases for a finite ticket type that is already live preserves its current public, held, sold, invited, bundled, and return-linked inventory. Hubbaly does not silently pull live tickets back into a future phase. Future releases can use later increases to the overall limit.

Let groups buy first

Members of selected groups in your hub can buy the same tickets before everyone else. They use the same stock, and pay their member price if you have set one. Hub Owners, Admins and Managers can set this up.

  1. In the ticket’s Sales step, choose On a set date and set Start date and time (UK time) to when everyone can buy.
  2. Under Buy first, choose a group and its earlier date and time. You can add up to ten groups. Times use the London clock.
  3. Review and publish the change. Members of those groups can buy when their sale opens.

During the early sale, eligible members see their group’s sale message. Everyone else sees the date when they can buy. A hidden group is named only to its own members.

Waiting-list offers wait until the public opening and use the tickets still available then. If members have already bought every ticket, everyone else sees it sold out when the public sale opens.

Changing the groups or their dates affects who can start a new purchase. Tickets already bought keep their price, and someone who has already reached payment keeps the price they agreed.

Ticket information for buyers

Use ticket information when buyers need practical details beyond the standard checkout policy.

  • Event ticket notes in Event -> Admin -> Tickets provide shared information for every ticket, such as arrival details, dress code, ID checks, accessibility information, or house rules.
  • In normal ticket setup, leave Add information for this ticket clear when this ticket needs no extra information.
  • Select Add information for this ticket to add details that apply only to that ticket. Buyers see them after any Event Ticket Notes.
  • Existing tickets that were previously set to replace Event Ticket Notes keep that behaviour when edited. Normal ticket creation does not offer that legacy override.
  • Ticket notes support markdown paragraphs and bullet lists.
  • Buyers only see these notes after they choose a quantity for that ticket type on a ticket-selection surface.
  • The Reuse from this hub picker copies a previously used note into the current editor as a starting point. It does not stay linked to the original.

Buyer limits

Use buyer limits when you want to stop one account from buying too many tickets.

  • Set an event or time buyer limit if you want one person to have a total ceiling across all ticket types and orders.
  • Set Tickets per buyer only if one ticket type needs a stricter limit, such as VIP or early access. This also applies across all orders.
  • Strict members-only events with guest tickets off do not show this extra setting. One buyer may still buy for other active members, while the platform limits each checkout to 10 of one ticket type and 20 tickets in total.
  • If the ticket limit matches an event or time limit, Hubbaly explains that it adds no extra restriction and can be left unset.
  • These limits apply to normal self-serve checkout only.
  • Complimentary tickets and staff-issued tickets are not blocked by buyer limits.
  • Neither ticket limit means per order. Both work across all orders, not just one checkout basket.
  • Buyer caps follow the original purchaser account, even if tickets are later transferred.
  • Hubbaly also has fixed platform checkout limits: up to 10 of one ticket type and 20 tickets total per checkout. These are not event settings.

Discount codes

Use Event -> Admin -> Tickets -> Discounts when you want to offer a specific ticket discount without changing the public ticket price.

  • Discounts belong to one event. Create a shared code when many buyers can use the same code, or a unique batch when each buyer should receive a one-use code.
  • A discount can be percentage based, a fixed amount off the order, or a fixed amount off each eligible ticket.
  • Scope a discount to all ticket types or selected ticket types from the discount form. You do not need to edit ticket types just to allow or block a code.
  • Buyers can use one code per order, and that one code can discount more than one eligible ticket in the order. For example, a staff discount can apply to the staff member and their partner when both tickets are eligible.
  • Optional start/end dates, total redemption limits, and per-buyer limits control when and how often a code can be used.
  • Copy link creates an event link that applies the code once the buyer chooses eligible tickets. The summary shows the code, the amount off and the new total before the buyer gives an email. The buyer can choose Remove or carry on at full price if the code does not fit their tickets. Hubbaly checks the code again when they continue to payment.
  • You can pause a discount without affecting tickets already bought. After the first redemption, Hubbaly locks the code value, discount type, and ticket scope so historical refunds and reporting stay stable. You can still rename it, extend the end date, or raise usage limits.
  • A 100% discount on paid tickets is still recorded as a checkout order, not a complimentary ticket.
  • Before checkout, Hubbaly uses what each ticket will actually cost after the discount when it explains the return route. A ticket reduced to £0 follows the immediate free-ticket route, while any ticket with a positive amount follows the conditional paid-return route when returns are enabled.
  • Refunds are based on what the buyer actually paid after discount. Refunding an order does not free the code usage back up; the code was used and remains counted.
  • Review performance from the Tickets discount panel, the Event Admin Sales tab summary, and the finance report/export.

Changing your ticket

Open My tickets, open your pass and choose Change. If you bought without an account, open View tickets in your ticket email and choose Change ticket.

If you hold several tickets for the event, choose which ones to change. They all move together or none of them do. Tickets assigned to someone else are theirs to change.

Choose another ticket or session on sale to you, then read Check the change. Hubbaly compares today’s prices, including any member price you can use, without discount codes. If the choice costs more and the organiser can take payments, choose Pay with the amount shown and complete the payment on Stripe. A dearer change includes a 50p Ticket upgrade fee, once per payment even when several tickets change together. Before paying you see Price difference, Ticket upgrade fee and Total. Your existing ticket details stay in place until the change is confirmed.

For a cheaper move, the review follows the event’s Moving to a cheaper ticket choice. With Refund the difference, choose Change and get with the amount shown. That amount uses today’s price difference, up to the money left from the ticket’s payments, less Hubbaly’s fee and the card company’s percentage on that difference. None of the card company’s fixed charge is deducted again. Before confirming you see Price decrease, Fees kept on the difference and You get back. It goes back to the card used for each payment, usually within 5 to 10 working days. A policy deadline also limits it. With No refund, the review explains the policy before you choose Change without a refund.

When there is no price difference, choose Change ticket or Change tickets. A cheaper move on another selected ticket does not reduce the payment for a pricier move; any refund is separate. The ticket change stays saved if its refund needs help, and the page tells you. One change email covers the tickets you changed together. See Moving to a cheaper ticket.

If the unpaid payment page expires, check the choices again from your ticket. If you paid but the change cannot be made, Hubbaly starts a full refund of that change payment. The page shows the refund’s progress. See Paying to move to a pricier ticket.

Date, time and same-price or cheaper ticket changes close 48 hours before your first session starts. A different session also needs to be more than 48 hours away. You can switch to a dearer ticket for the same date and time until your session starts. Every ticket you change together must still be open for that change. If we confirm payment too late to move the tickets, we refund the whole change payment. Your QR code and reference stay the same, including a saved or printed copy, and Hubbaly emails the new details. Event extras stay on their original session. Ask the organiser if those also need changing.

If you later give your place back after a cheaper move, the amount refunded is limited to that ticket’s price at that time, after the usual fees. It cannot exceed the money still available on your ticket.

On a phone, the pass puts Invoice, Transfer and Change in one row, showing only the actions you can use. Invoice is for the purchaser. If your updated pass cannot be loaded after saving, the page confirms the change was saved and offers Try again.

Let people change their own tickets (organisers)

Open Event Admin -> Tickets -> Rules -> Ticket changes. Let people change their own tickets starts on. Turn it off and save when people must stay in the session they booked. You can still change a ticket yourself from Sold tickets if you have Manage event sales.

Transfers

Before that ticket’s booked time ends, and when policy allows:

  1. Owner initiates transfer.
  2. Recipient accepts.
  3. Ownership updates and transfer history is retained.
  4. Member-only policy can block transfer if recipient already has an active ticket.

Transfer targeting rules:

  • Public ticket-access events can be transferred either to an existing eligible account or directly to an email address.
  • A ticket that only hub members can buy is the exception on a public event: it can be transferred to a hub member, not sent to an email address.
  • When the ticket owner searches for and chooses an existing hub member, that person sees the request in Alerts and can receive a phone notification when enabled. The alert opens the incoming transfer so they can accept or decline inside Hubbaly without using email.
  • Email-targeted recipients get a secure review link by email, can accept without joining the hub first, and can claim a full account afterward. If that address already belongs to a Hubbaly account, the request also appears in Alerts and can produce a phone alert when that person has allowed them. The sender is not told whether the address already has an account. If the request is cancelled, refunded, or voided before acceptance, that account gets a cancellation alert which opens the incoming-transfer context.
  • Holding a transferred public-event ticket does not automatically make the recipient a hub member or unlock hub-only features.
  • Members only ticket-access events still require transfer to an eligible existing account through the in-app recipient search.
  • On an Invite only hub, the ticket owner cannot use the normal hub link to admit a new recipient. For a members-only ticket, ask a hub organiser to invite the person before searching again. A public ticket can still be sent directly by email.
  • A transfer invitation lasts for up to seven days, but it ends sooner when that ticket’s booked time ends. For a ticket covering the whole event, the event end is used instead.

Refund policy note:

  • Tickets are dated event access, so buyers should not assume a change-of-mind refund is available.
  • If an event is cancelled, moved, rescheduled, or materially changed, direct refund handling follows the organiser’s obligations, Hubbaly platform rules, and payment-provider requirements.
  • Refunds always go back to the original purchaser.
  • A ticket designated to someone else at checkout can still be requested from the original purchase when it has not been later transferred, but the designated holder must approve before Hubbaly releases the place.
  • Pending holder approval does not lock that holder’s pass. The holder can approve the return, keep the ticket, or transfer it before any place is released. If they transfer it first, the approval request is cancelled because the requested holder no longer owns the ticket.
  • Once a ticket is transferred after checkout, it must be transferred back to the original purchaser before a self-serve refund can be requested.
  • Members plus guests events allow the original purchaser to hold extra guest tickets, so transfer-back should not be blocked just because the purchaser already has one active ticket.
  • If a strict members-only event does not allow guest tickets and the original purchaser already has another active ticket for that event, Hubbaly can show Transfer back blocked because moving the ticket back would give that purchaser two active tickets in an event that only allows one member-held ticket per person.
  • Transfer-back can be blocked by strict members-only holder rules, so some cases need organiser/support handling instead.
  • Event Admin standard refunds retain the Hubbaly fee and Stripe processing shown in the refund breakdown.
  • Event Admin can also choose a full-refund override when the organiser should absorb those retained fees instead.

Waitlist and returns

Open Event admin → Sales → Waitlist and returns to see who is waiting, which tickets are held, and what has happened to returned tickets. You can also open it from Tickets.

  • The waitlist opens when an eligible ticket sells out and the waitlist is on. When a place becomes available, the next eligible person gets a held ticket with a deadline to buy. If they pass or run out of time, it moves to the next person. A request is not a sale.
  • A free return stops the original ticket working and makes its place available straight away, offered to the waitlist first. There is no refund to wait for.
  • A paid return waits for someone else to buy the place before the original buyer is refunded, minus the fees. A refund is not guaranteed. Unsold tickets already on sale are sold before matching returned tickets.
  • On the page, read Held until for a buyer’s deadline and the returned ticket’s progress for whether it is waiting, held for someone, or being refunded. Every change shows the history.
  • To change the settings, choose Change on the page, or open Tickets → Rules → Sell-out recovery. Returns are optional for each eligible ticket type; they are separate from an organiser cancelling or refunding an order.

For the full rules, read Sold-out waitlist and Ticket returns and released tickets.

Sold-out waitlist

Use the waitlist when tickets are full and you want to keep a clear order for who gets the next chance.

Waitlist lifecycle: waiting, then invited, then ticket bought. Expired or passed invites move the place to the next person.

Waiting

You're in line. No action needed.

Invited

A place opened. You get a timed email invite.

Ticket bought

You buy within the window. You're in.

If an invite expires or is passed on: the place goes to the next person automatically and that request comes off the list. You can also leave the queue at any time.

How long a waitlist offer is held, from 48 hours a month out down to 30 minutes on the day

How long an offered place is held, based on how close the event is. Save it or share it with your community.

  • People join the waitlist from the event page after tickets sell out.
  • Event waitlists are tied to Hubbaly accounts.
  • On public event pages, signed-in viewers can join directly and logged-out viewers go through an account handoff before the entry is created.
  • For sold-out member tickets on an open hub, the handoff can create the hub membership and the waitlist request together when policy allows.
  • If the hub requires published terms before joining, Hubbaly shows those terms first and creates the member-ticket waitlist request only after acceptance.
  • In an ordinary direct ticket queue, each requested ticket creates its own queue slot. Joining for 2 adds 2 slots, and adding 1 later appends one more slot to the back of that direct queue.
  • One buyer can hold up to 20 active waitlist requests per queue.
  • The waitlist stays open for as long as ticket sales do, including during the event when an end time is set.
  • Buyers can see their queue position when they join and again on the waitlist management page under Your waitlist requests.
  • Buyers can remove individual waitlist requests or remove several at once instead of clearing the whole waitlist every time.
  • Waitlist joins still respect event-wide and ticket-type buyer caps.
  • A successful waitlist join sends a confirmation email. Ask buyers to check junk/spam and mark Hubbaly mail as safe so timed purchase offers are not missed.
  • If several ticket lists share the place that has opened, Hubbaly offers it to the person who has waited longest and can use it. It moves past people whose ticket is still full or who have reached their buyer limit. A returned paid ticket being sold again stays with its own ticket list.
  • A schedule made only from shared bookable-time tickets uses one event queue, not a separate queue for every time or ticket. This prevents someone jumping ahead by joining every slot. When a time opens, the oldest eligible person is offered that exact time and can choose any eligible ticket type for it, pass that time to the next person while keeping their original place, or leave the queue.
  • In that any-suitable-time queue, each requested place means one separate appointment. A buyer can choose several places when joining and add more later from the same event-page card. The places keep separate queue positions, but the buyer receives only one live offer at a time, and later offers may be for different times.
  • On a public event, someone outside the hub can choose Join the waitlist for any suitable time and sign in to request public tickets. The offer email opens the event’s waitlist. Take this time opens checkout for the held ticket. They can clear the choice to join the hub if it appears.
  • The number of extra places offered respects the event’s buyer limit and places already waiting. On a members-only event that does not allow guest tickets, each member may hold or wait for one place in their own name. A ticket they bought for another member does not use their own place.

What if more than one time becomes free?

A person waiting for any suitable time can hold only one offer at once. If two different times become free, Hubbaly may offer the first one and leave the other on sale while the person decides.

If the person chooses Pass this time, they keep their place in the queue for a different time. Hubbaly rechecks the other times shortly afterwards. If the second time is still free, it is held and offered to them; the time they passed moves to the next eligible person or goes on sale.

Another buyer may buy the second time before the pass, so Hubbaly can offer it only if it is still free when the queue is rechecked. Passing rejects that exact time: if both free places are for the same time, both may be on sale after the pass.

Creating that next offer can take up to about a minute after the pass. Once Hubbaly sends the new held-time notification, an event page that is already open checks the waitlist again and shows the held time. Opening the notification does the same, so the buyer should not need to reload the page.

  • If an event mixes shared and exact-time tickets, the organiser must choose one clear strategy for the whole event: one anytime queue or the established direct ticket/time queues. Hubbaly asks only when that mixed product setup exists.
  • Queue priority is absolute. A time held for the next eligible waiting buyer cannot be taken through public checkout while the queue offer is being prepared, retried, or answered.
  • Joining a waitlist does not preserve the previous sales phase price. Buyers see the expected next phase and price, but the organiser may change a future phase before an offer exists.
  • Once Hubbaly issues a timed primary offer, its displayed base price is protected until that offer expires, even if another sales phase opens.
  • When a sales phase releases more tickets than the waiting cohort needs, waitlisted buyers can receive timed offers while the surplus goes on general sale at the same time. A general-sale notice never reserves a ticket or reveals an exact stock count.
  • Release notifications tell the buyer they are next in line, include the exact Purchase by deadline, and the waitlist management page shows that same deadline while a slot is released.
  • How long buyers get scales with how far away the event is: roughly 48 hours when the event is a month or more away, about a day at one to four weeks, shorter as it approaches, down to 30 minutes on event day. Quiet queues get a little longer and busy queues a little shorter.
  • Deadlines avoid the middle of the night: short windows that would expire overnight roll forward to 10:00 UK time, and no deadline ever lands after ticket sales close.
  • A failed checkout (for example a declined card) does not cost the buyer their place while their window is still open; the same offer link keeps working until the deadline.
  • The release email and waitlist management page also let the buyer use Pass to next person if they no longer want those tickets.
  • If the buyer passes or misses the deadline, that slot moves to the next person in line automatically and the earlier buyer gets a closure message with a rejoin link.
  • Places can reopen because stock is added, a checkout hold expires, or a ticket is cancelled/refunded back into normal inventory.
  • If an organiser increases ticket capacity after sellout, Hubbaly automatically offers the newly opened seats to the front of the relevant waitlist instead of leaving those buyers stuck waiting.
  • The platform only sends new offers for seats that are actually free at that moment. Live checkout reservations still count as held inventory, so a large capacity increase does not over-invite beyond real availability.
  • If one ticket type is sold out while another is still on sale, the sold-out ticket type can show its own waitlist entry point without blocking the other ticket type from being purchased.
  • Every reopened place is offered to the people waiting before anyone else can buy it, however many reopen.
  • On Waitlist and returns you can remove someone who no longer wants a place. If a ticket is held for them, it moves to the next person in line.

Status guide, in the words Waitlist and returns uses (Event admin, Sales):

  • Waiting: the person is still in line, numbered by their place in their ticket’s own queue.
  • Held: a ticket is held for them until the time shown, with the time they have left to buy. It shows Paying now while they are at checkout. If they do not buy it in time, it moves to the next person.
  • Bought from the waitlist: they bought a ticket that was held for them.
  • Left or removed: they left, passed a held ticket on, their time to buy ran out, they got a ticket another way, or an organiser removed them. Every change on Waitlist and returns says which.

Complimentary tickets

A complimentary ticket is a gift. The holder sees Complimentary, Received and From with the hub’s name. Organisers still find its record in Orders, labelled Complimentary, with the holder’s name and Issued by the organiser. The holder’s name opens their Hub person record. Opening the record shows For, Issued by, Issued on and Ticket given, without checkout or amount-paid lines. Sold tickets also names the issuer. Under View email invitations, hub owners and admins can see who sent each invitation. Giving a ticket does not put a purchase in the giver’s own Purchase history.

Sold figures leave complimentary tickets out. When there are any, their own line says how many are complimentary in Sales, Session sales, Reports, Hub Finance and the weekly Hub Finance brief. Complimentary records still count as Orders. Attendance and room limits still include their places.

In the attendees spreadsheet downloaded from Hub Finance, a complimentary ticket leaves Purchaser Name and Purchaser Username blank. Order Source says Complimentary, and the final Issued by column names the organiser. The holder remains the attendee.

Giving somebody else a ticket does not add a new record for you in People. If you already have a record, your issuing history stays there.

After accepting a complimentary ticket, the holder gets one email from the hub with View ticket, the event page and calendar links. If the event has a required form, Sign the form comes first; there is no separate forms email, but the form alert in Hubbaly and on the phone stays. The email includes the event chat only when the holder can join it, and shows no money lines. The organiser who gave the ticket receives Complimentary ticket accepted or Complimentary ticket declined in Hubbaly and on their phone, never by email. They can switch these notices off under Ticket updates. A declined invitation sent by email names nobody. Nobody gets a giver notice when an offer expires, is withdrawn or is given to the organiser themselves.

The holder can choose Return this ticket in My tickets to give their place back. Returning a free ticket explains when the action is available.

Use complimentary tickets when you want to issue a free place without sending someone through normal checkout.

  • Good for staff, VIP guests, media, partners, or promo attendees.
  • Search current hub members by name or username to offer a ticket in Hubbaly. Owners and admins can instead choose Invite by email and enter up to 50 addresses, including people who do not have an account yet.
  • Email offers never expose an account search or tell the organiser whether one exists. Hubbaly always sends the email. Behind that private boundary, an exact verified account also receives the offer in Hubbaly and by Push when enabled.
  • The person opens the private email link, then signs in or creates and verifies an account. They can review the event and ticket before accepting. The email address is not placed in the browser address bar.
  • Choose whether accepting should also join the person to the hub. Hub-members-only events always require this. Hubbaly shows any current Hub Rules, membership terms and required shared details before the person joins.
  • Open View email invitations to see every email offer for the event: the address it went to, when it was offered, and whether it is pending, accepted, declined, expired or revoked. A pending offer can be resent or revoked. Once an offer is declined, expires or is revoked, Hubbaly clears its address, so only the first letter and the part after the @ are shown.
  • An email offer that is still waiting counts as issued and awaiting acceptance on the Complimentary line, so the totals show offers that are out before anyone has accepted.
  • If the event has multiple ticket types, pick which one the comp should mirror (name and who can receive it). For single-type events no ticket-type choice is needed. Sessions that have already ended are not offered. If that type has several live sessions, choose the exact session for this complimentary offer; a single live session is included automatically.
  • The chosen session appears in the invitation, notifications, organiser history, acceptance screen and pending ticket. It stays the same if the ticket type changes later, and a new offer stops being available when that session ends.
  • Comps draw from a hidden Complimentary allocation rather than paid sale stock, but they still consume physical event or per-time capacity. A multi-session type’s comp uses only the chosen session, so that slot is no longer available to another buyer.
  • A comp cannot bypass a finite physical capacity. If there is no remaining place at the selected event time, choose another time or free capacity first.
  • Complimentary tickets are non-transferable by the holder. An admin can reassign a comp to another member if needed. Where the event allows one ticket per member, that member must not already hold one.
  • The attendee receives a normal ticket and is added to the attendance list.

Ticket returns and released tickets

Returns let eligible ticket holders give a place back when you have enabled them. Free tickets go back straight away; paid returns wait for the place to sell again before a refund is sent, minus the fees. The rules below explain who can return a ticket and what happens next.

About ticket return requests

If enabled for the ticket, this optional Hubbaly feature lets eligible free and paid ticket holders give a place back. It is separate from cancellation or material-change refund rights.

Free ticket returns

The signed-in purchaser can return an eligible free ticket from Account → Purchases while they still hold it. The ticket stops working immediately, its sale allocation is restored, and its exact place goes to the waitlist first or back on sale when nobody is waiting. There is no refund or replacement-sale step, and a free ticket never appears in the paid return preview. A fully discounted ticket follows this path because the buyer paid nothing.

Complimentary, staff-issued, bundled, transferred, checked-in, invite-only, cancelled-event, and already-started tickets remain excluded. Email-only guests contact the organiser because this self-serve action requires the purchaser’s signed-in account.

An eligible paid ticket uses the existing conditional return queue. The queue protects normal ticket availability, and the replacement buyer receives a newly issued ticket from the organiser only when Hubbaly releases a place.

  1. Original purchaser starts from Account → Purchases.
  2. Purchaser-held tickets queue immediately.
  3. Clean designated-at-checkout tickets ask the current holder to approve before Hubbaly releases the place. The holder receives an in-app notification and email, and the pass remains valid while they decide.
  4. Once a ticket is queued or holder-approved, the original ticket is locked from transfer/check-in.
  5. A released ticket hold can then be offered to the waitlist.
  6. Compatible primary ticket releases are sold first. Return matching resumes after that primary inventory is bought or otherwise no longer available.
  7. If a buyer passes or the timed hold expires, Hubbaly offers that slot to the next eligible waitlist buyer before falling back to public checkout.
  8. The original purchaser’s refund is triggered only after a replacement purchase succeeds (Hubbaly fee and Stripe processing retained under the standard policy).

Important policy notes:

  • Refund is not guaranteed until a replacement purchase completes.
  • A new sales phase may delay a return request because primary tickets are always sold before compatible returned places. The return keeps its existing queue order while paused.
  • The original purchaser’s refund remains based on their original payment and stored fee snapshots, never the current sales phase or replacement price.
  • An already-issued returned-ticket offer stays valid and price-protected until its deadline if a new primary phase opens later.
  • Holder approval is not a refund and not a return request. It is only consent from the attendee currently holding a clean designated-at-checkout ticket.
  • Ticket returns are a Hubbaly product feature, not a legal refund obligation.
  • Unresolved requests expire when ticket sales close (the event end time for multi-day events).
  • Waitlist-first released tickets use the same automatic You're next in line, Purchase by, and Pass to next person flow as the standard sold-out waitlist.
  • If a released Ticket Return has already matched another buyer and is being held in that buyer’s checkout, Hubbaly can show Released ticket held in checkout instead of offering the same seat again.
  • If a timed offer expires, or the current buyer passes, that buyer gets a closure/rejoin message and the slot continues through the next waitlist-or-public fallback step.
  • REFUND_PENDING can persist temporarily when Stripe/Connect settlement requires retry/reconciliation.
  • Ticket holders usually start this from Account → Purchases, and each live ticket page now includes a shortcut back to the matching purchase row.
  • Organisers turn this on per ticket type in Event Admin → Tickets. The same choice controls both modes, but its wording follows the ticket’s saved price: immediate place return for free-only tickets and replacement-sale refund for paid-capable tickets. Free-only returns remain available even when the platform’s paid return pipeline is not active.

Designated tickets at checkout

One payer can assign tickets to other members at checkout:

  • Payer remains financial source-of-truth,
  • Ticket holder and payer can differ,
  • Refunds return to original payer,
  • Ledger keeps ownership and refund states explicit.

How that changes by ticket-access mode:

  • Members only: after the buyer’s own ticket, every extra ticket must be assigned to an active hub member before checkout can continue.
  • Members + guests: assigning existing members is optional. Use it when you already know which member should hold a ticket. Any extra tickets you leave unassigned stay on the buyer account for now, which lets a member reserve places for guests on private events without naming them first.
  • Public: people can usually buy directly for themselves instead of relying on member assignment, and signed-out guest checkout is available only when the event is also public-listed.

Critical event updates

  • Time-change alerts should only be sent for actual time changes.
  • Time text should be human-readable.
  • Non-time edits should not be labelled as time changes.

Identity verification for events

Identity verification is an advanced capability for selected communities. Use it only when a community sometimes confirms identity in person and needs a reusable trusted state for later events, without storing sensitive ID documents online.

Common organiser use cases:

  • Name or ID-style checks at entry,
  • Private or trust-sensitive community events,
  • Marking someone as known or identified in person so later events can rely on that community-level trusted state.

How it works:

  • Hubbaly enables it for a specific community.
  • After that, the hub then chooses whether to turn identity verification on.
  • Hub -> Admin -> Settings then chooses whether to turn identity verification on for that hub.
  • Once the hub enables it, specific events choose whether to use it.
  • Members see calmer Door-check details wording on member-facing surfaces instead of the system label.
  • Members can save their legal name and, if useful, an optional private photo from Hub -> Verification.
  • Owners/admins, or event staff with VERIFY_MEMBERS, can review those details or mark someone verified in person.
  • That verified state belongs to the hub, so future events can reuse it without asking the person to upload sensitive documents.

What is stored:

  • Legal name,
  • Optional private photo,
  • Trusted/reviewed state,
  • Review history for who confirmed or revoked it,
  • No sensitive ID documents stored online.

Event setting options:

  • Off: do not use identity verification for this event beyond normal ticket validation.
  • On demand: staff can open identity details after a successful online scan when they need an extra check.
  • Used at door: identity verification is part of the normal door workflow for this event after ticket validation.

Important limits:

  • Ticket validation still stays the main event-day step.
  • Scanner review only appears after a successful online validation.
  • Offline scanning can continue, but identity verification review does not.
  • Hub admins can also review or revoke someone’s trusted state from Hub -> Admin -> Verification.
  • Communities that have not been enabled by Hubbaly do not see this workflow in normal hub or event admin settings.

Event Day scanning

Use Event -> Admin -> Scanner for live check-in.

  • If the event attendance registration is Off, the Scanner tab is hidden from navigation.
  • Owners/admins can still open the disabled scan page from a direct link to confirm why it is unavailable and jump back to settings.
  • Managers and staff are redirected to the next visible admin workspace instead of staying on a disabled scanner route.
  • Scanner opens in manual mode first so desk teams can search immediately and deliberately switch into camera use when they need it.
  • Tap Use camera for QR scanning. The camera sits directly under the title, with the last person let in and Undo check-in in the slim strip below it.
  • Camera mode is best for phone-based QR scanning.
  • Manual input/search is useful for desk workflows and hardware scanners. Its result strip and Undo sit directly below the search box.
  • For very large events, scanner manual mode becomes search-first instead of showing a passive browse list.
  • Offline pack download is available in the scanner wherever offline scanning is enabled, including the app installed from your browser. Keep the scanner page open before losing connectivity: a fresh page load still needs a live connection.
  • Offline scanning should be prepared before losing connectivity, not after.
  • The Offline scanning panel says Offline verification: ON when the phone can check tickets without signal. If it says Offline verification: not on this phone, the phone’s browser cannot check a ticket’s code by itself, so without signal it would turn every ticket away. Use another phone for the door, or keep this one on a connection. Older iPhones that cannot update past iOS 16 are one example.
  • A good ticket fills the screen with Let in, the person’s picture, name and @username. Without a name it shows @username; a guest shows their order name and Guest, or Guest ticket if no name was given. A drawn face stays visible until the small photo loads. The ticket name has its own line, followed by its number and six-letter reference, such as #148 · Q7MRT2, when the phone knows them. The result closes after about two seconds, or sooner if you tap it; events using door-check details keep it open for a tap.
  • A check-in made from the phone’s saved list is also green and says Saved on this phone. It is kept to send when the connection returns. No signal: still scanning stays in the title row.
  • Already in means this ticket has already been checked in, at the time shown. This warning helps staff stop two people using the same QR code: someone else may be showing a copy. It does not prove that the person in front of you is the same person returning.
  • A single-date pass shows Welcome in. instead of its QR code once it receives the check-in. If the returning person has no code to show, use manual search by name or ticket reference. An older screenshot or a phone that has not received the check-in can still show a code; a pass covering more dates may also keep its code for those dates.
  • Only choose Let back in if you are satisfied this is the same person returning. Manual search also shows In at with the first check-in time, the same warning and Let back in; finding the ticket by name or reference does not prove who is presenting it. The green result shows the return time. A confirmed return is recorded without changing the first check-in or counting the ticket twice. Undo on that result or the strip removes only that return record.
  • With no connection, only choose Let back in when you are satisfied it is the same person returning. It still turns green and says No signal: not noted. The phone did not send a return note and does not keep it to send later. Separate scanner phones cannot see each other’s latest check-ins until they reconnect.
  • If the phone sends a return note but gets no reply, the green result says Return not confirmed. The note may already be saved. Undo still targets that return when the connection answers. If Undo fails, it stays available to try again.
  • If Undo check-in cannot reach the server within a few seconds, the result says Undo not confirmed and stays, with its Undo check-in, so you can try again. The person may still be checked in. If the server answers later, the result goes by itself.
  • Forms not signed shows the supplied reason and has no override button. Not valid shows why the ticket cannot be used; Not checked means the check failed and asks you to scan again. A code the phone can tell is unreadable says Not valid even without signal. These stops stay until you tap, and the camera reads no new ticket meanwhile.
  • If the scanner says “Check the event on this ticket. This code could not be checked here.”, compare the event on the guest’s ticket with the one at the top of your scanner.
  • Review Recent scans on this device if someone disputes a scan. Each row shows what happened, who, the ticket name, number and reference, and the time. Returns say Let back in; check-ins waiting to send say saved on this phone. A refusal includes its reason. This device’s list is temporary.
  • If the event header cannot load, tap Home above the scanner to open the Home page saved on your phone.
  • If the event uses private door-check details, the panel appears only after a successful online validation and only when an operator intentionally reveals it.
  • Staff need the separate VERIFY_MEMBERS permission to use that panel unless they are already a hub OWNER or ADMIN.
  • Offline scanning can continue, but private door-check review does not.
  • Scanner review is one option, not the only one: hub admins can also review members from Hub -> Admin -> Verification.

Event Day and attendance records

Use Event -> Admin -> Event Day for the live roster during the event. After the event, the same workspace relabels to Attendance records, where you can still check people in.

  • If attendance registration is Off, Event Day stays visible for organisers and other roster-capable roles, but it becomes read-only and Scan stays hidden.
  • Event Day is the place to review checked-in tickets, who is not in yet, blocked arrivals, staff-on-site status, and recent arrivals from one canonical roster.
  • The main summary answers the door question first: how many tickets are in and how many are still to come.
  • The readiness area is an attention panel, not a second attendee list. Before the event it highlights preparation gaps, during the event it becomes Needs attention, and after the event it becomes attendance follow-up.
  • Use the attention panel for counts and the first few people who need action; use the roster, filters, search, and scanner for the full participant list.
  • People to review is for actionable work: missing required forms, forms that need re-signing, and post-event feedback follow-up. Refunded, transferred, voided, or replaced tickets stay in summary counts for audit context; they are not listed as people to review.
  • Roster rows show profile display names first, then @username when a display name is blank. Uploaded avatars follow profile-photo visibility rules, including connection-only photos; generated fallback avatars are unique per account.
  • On larger events, Event Day opens search-first with summary, filters, and a small recent-arrivals feed instead of a long passive roster.
  • Review the policy banner first so operators know what counts as confirmed.
  • On either check-in setting, choose Check in beside a person to record their arrival. If they have several tickets, choose the one to check in.
  • On a ticketed event, Check in checks in the ticket too, so the door count and reports follow. Events without tickets record the person’s attendance.
  • On a ticketed list without a date selector, Remove clears the person’s check-in and all their checked-in tickets. After no-show marking, those tickets count as no-shows again.
  • If Showing offers dates or times, Remove in Whole event clears only the attendance record. Tickets stay checked in. A selected date or time has no Remove; only the Scanner’s immediate Undo can undo that check-in.
  • Check-in from the list has no closing time. The Scanner closes 4 hours after the event ends.
  • Keep notes short and factual if you check someone in by hand.

Incident logging and follow-up

Use Event -> Admin -> Incidents to capture operational problems with an audit trail.

  • Report incidents when something operational or safety-relevant happens.
  • Report times and outcome expiry dates use London time, wherever your device is. When the clocks go back, choose the first or second occurrence of a repeated time. A time skipped when the clocks go forward cannot be used. Reports for British Summer Time dates made before this correction may still read an hour late; past records have not been changed.
  • Apply outcomes only after the facts are clear enough to explain the decision later.
  • Use this for durable records, not casual back-and-forth discussion.

Post-event reports and reconciliation

Use Event -> Admin -> Reports after the event to review what happened.

  • On the night shows ticket sales, arrivals, required forms and incidents. Saved offline check-ins count after the scanner reconnects and sends them.
  • Money shows sales, fees, refunds and the money kept. Read any warning or data check before treating the figures as final; a refund still waiting to finish is different from a failed one.
  • Use Download PDF for a copy to share, or the spreadsheet when you need the figures in a table.
  • People only see the parts of the report their event permissions allow.

Event-day quick checklist

  • Scanner operators are assigned and tested.
  • Required forms readiness is monitored.
  • Staff escalation owner is known.
  • Critical update path is ready.
  • Incident logging path is verified.

Where to go next

Last updated on