All updates

Staff date commitments, private events, feedback forms, and connections

Invite staff to the exact dates they can do, run private invite-only events, build feedback forms with ratings and templates, and connect with people you meet at events.

  • events
  • forms
  • tickets
  • trust
  • chat
  • photos

Invite staff to the dates they can do

Staffing a multi-day event no longer assumes everyone works every day.

  • When you invite staff to an event with more than one date, each invitation starts with no dates ticked. The dates you pick for each person are a deliberate choice, and you cannot send until you have picked at least one.
  • Recipients accept only the dates they can do. Their inbox and the email invitation page show each date as accepted, awaiting, or declined.
  • Invitation alerts and emails spell out the full date offer, with dates and times written out in full, and a compact alert row expands to the complete list on demand.
  • Access follows acceptance: live event and session access, Event Day, and staff tools all honour the dates a person actually agreed to.
  • Changing the event schedule preserves existing agreements. Adding a date never silently signs anyone up for it, and the change links you back to review staffing.
  • The staff workspace groups each person’s accepted, awaiting, and declined dates so gaps are easy to spot. Unused roles can be deleted, and archived roles restored.
  • An email invite that can be used several times now reserves a staff place for every remaining use, so a shared link can never promise more places than you have.

Private invite-only events

  • A new “Private, invite only” visibility keeps an event out of discovery, lists, search, and shared surfaces entirely, hidden even from hub members.
  • Invitations open it up: only people you invite can see the page, its content, and checkout.
  • If someone without an invite ends up with the link, the event simply reads as not found. It never confirms it exists.
  • Waitlists and ticket returns are not offered on private events. Sell-out recovery needs an open audience, so setup says that clearly instead of showing switches that could never work.

Feedback forms, rebuilt

  • The feedback builder now shows exactly what members will see: each question is a card rendering the real member control, not a schematic.
  • Two new question types: a 1 to 5 rating scale and single choice. Both work properly with keyboards and screen readers.
  • Templates make feedback reusable: start an event’s form from a hub template, or save a good form as a template for future events.
  • Publishing a form and requesting responses are now separate, deliberate steps. The request confirms its audience with a live recipient count, and every request is audited.
  • Participants always receive the latest published version of a form, never a stale draft or an unpublished edit.

Event schedules, guided

Setting up a multi-date event is now a guided task rather than a form to fight.

  • When you create a ticketed event you answer one question: how does this event run? One continuous period, or separate dates or times.
  • Helpers build the dates for you: consecutive days, repeating dates, or add them yourself. You preview and review every start and end before saving, in London time, with clock-change oddities handled.
  • Schedule setup opens as its own focused step, Structure then Dates then Review, instead of a mini-wizard squeezed into the create form. Close it and resume later without losing anything; nothing is committed until you choose “Use schedule”, and the browser Back button cannot throw work away.
  • Adding dates later appends to the existing schedule without touching current rows, and dates always keep chronological order.

Dates that read true everywhere

  • Multi-date events now show one clear, accurate date range everywhere: Home, Discover, hub lists, and the event page, which also gains a strip of its dates.
  • The event calendar download now adds one entry per date, not a single block spanning the whole run.
  • Confirmation-email calendar links match what was actually bought: the chosen show for pick-a-time tickets, the covered days for a selected-days pass, the first upcoming date for a whole-event ticket.
  • Emails across the board, from confirmations and reminders to waitlist notices, refunds, campaigns, and reports, now name the right dates for what each person holds. When a date cannot be stated with confidence, the email leaves it out rather than guessing.
  • When buying, each pick-a-time ticket keeps its own date choice, and that choice survives signing in, joining the hub, accepting terms, waitlists, returned seats, and the Back button.
  • Event Day now scopes to one show of a multi-session event, with a selector to switch shows, and desk check-in enforces the same safety gates as QR scanning.

Share your profile and connect

  • Your profile now has one “Share and connect” sheet, with a QR code, an invite link, and the usual share options, in place of the separate QR and share actions. You can open it from your profile, your account, and your connections page.
  • You can now connect with people you share an event or hub with. Attending the same event lets you see each other’s profile and photos, so you can find someone you met on the night.
  • A private “My connections only” profile still shows a wall that lets someone send you a connection request, without revealing whether the profile exists.
  • Invite links carry a clean, branded preview when you share them.

The door stays open after the event

  • The door scanner now stays open for 4 hours after the end time, so late arrivals can still be scanned in. A banner explains scanning is open for stragglers, and the scanner shows as closed once the grace window passes.
  • Ended events no longer vanish from home. As an organiser you keep a “Wrap up” entry for 7 days; ticket holders and staff keep a “Just ended” entry for 48 hours.
  • The event page and tickets now read as ended: an “Ended” chip, a “This event has ended” notice, no buy button, and past tickets that say “Event ended” instead of “Expired”.
  • Anyone still on a waitlist when the event ends is closed out automatically.

A richer post-event report

  • 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.
  • Two new charts sit under the overview numbers: an Arrival Curve of check-ins across the door window, and a Sales Pace line tracking sales up to doors against your capacity. Both now appear in the PDF export too.
  • Refunds are split by who or what issued them, with a list of every refund and its source.
  • A new Waitlist and Returns section shows how the queue performed: joined, invited, bought through the waitlist with a rate, invites expired, still waiting at close, and returned seats passed on to new holders.
  • The overview now shows check-ins as a percentage of tickets, and the same refund lines and waitlist section appear in the finance spreadsheet.
  • The entry section now says only what recorded evidence supports: a reconciling “No Recorded Check-In” breakdown replaces the old blocked-attendees guess, and its document state is frozen once the door window closes, while late check-ins still count.

Add a photographer to your event

  • You can now add someone as event staff with just an Upload Photos permission.
  • A photographer can add photos and videos to the event’s album while it is still limited to admins and managers, and their uploads skip the approval queue. They can even create the event’s album if it does not exist yet.
  • They can manage only their own uploads, with no album settings or curation controls.
  • A photographer who is not a hub member can still open the event page and reach the restricted album. When their staff shift is marked complete, that access stops.
  • The Photos section on the event page no longer vanishes on a slow connection: it stays put while loading, offers a retry if the request fails, and shows “Create album” once the event is confirmed to have none.

Share two versions of the same album

One album can now serve two audiences at once: the people it was made for see everything, while a wider audience sees only a curated selection.

  • For an event, that means attendees can have all the photos, while the whole hub, or the public, sees a more limited version of the same album with just the set you choose to showcase.
  • You build the wider version by making individual photos or videos more visible than the album’s default. Each item you widen joins the curated version; everything else stays with the core audience.
  • Both versions live at the same address, and each viewer sees only the version they are allowed. The wider audience sees a view clearly labelled as a selection, with honest counts, and never gets downloads, photo locations, linked chat, or any management controls.
  • Making the first item more visible is the deliberate publishing step. Restricting or removing the last one closes the wider version again.
  • A privacy fix keeps draft, archived, hub-only, and invite-only event albums out of photo timelines for anyone who cannot see the event itself.

For organisers and admins

  • Chat channel settings are now a compact, summary-first sheet: what the channel is at the top, your own settings grouped below, and the member list brought forward. Each setting opens its own focused editor.
  • Creating an event now leaves you with a clearly labelled draft. Ticketed, collect-interest, and no-ticket events all show a truthful publish state and exactly what publishing will do.
  • Posting an event update now confirms its audience with a live count of who will be notified.
  • The campaign test-send says who it can reach, and a rejected address explains itself. Campaign emails render their call-to-action as a proper button in your hub’s colours.
  • On invite-only hubs, share links now work as invitations: an active organiser link grants access, while inactive, view-only, or unknown links do not.
  • The Waitlist and Returns overview can now load older activity, so the ledger goes back as far as you need.
  • The staff picker is results-first on mobile, so results are not buried under the search controls.
  • Hub Recent memories now follow upload order, and album covers are always ones the viewer is allowed to see.
  • Duplicating an event no longer copies staff assignments, so a copy never starts with silently pre-accepted staff. Documents, settings, and images still copy.

Reliability and polish

  • Saving a photo on iPhone or iPad now opens the native share sheet, so it can go straight into your photo library.
  • The door camera recovers on its own if the video stream freezes after the phone sleeps, and reads marginal codes with the phone’s built-in scanner.
  • Event and hub pages hold their shape while loading, so flyers and content no longer jump around as the page fills in.
  • An album you are not allowed to see now reads as “not found” rather than “no access”, so it never reveals that it exists.
  • Event Day no longer refreshes in a loop for an event whose first date is months away.
  • Coming back to the app after a while no longer shows a false signed-out screen: the app rechecks your session when it wakes.
  • Scrolling is smoother: the bars at the top and bottom of the screen no longer blur the content passing beneath them, which caused flicker on some phones.
  • Telegram was removed from the share sheets.

Behind the scenes

Adds a staff date-commitment model serialized under the event schedule lock, invite-only access grants that fail closed across discovery, content, and checkout, and a single canonical feedback field renderer shared by the builder, templates, and member forms with versioned publish and request flows. Introduces an album read-mode resolver (full, filtered, none) with probe-based discovery and grant-only pagination, a focused schedule dialog with guarded browser-history traversal, an order-coverage resolver so email calendar links match the purchased sessions, session-lens Event Day caches with server-side desk check-in gates, frozen entry-report requirement snapshots, a shared-event participation resolver for connections, and server-drawn report charts shared by web and PDF. Moves the runtime to Node 24, reconciles auth on app foreground, and drops backdrop blur from scroll-path chrome.

Keep up with what we ship

Follow new releases by email or feed.