Event settings

Only coordinators can open the settings page, and most dials are theirs to turn; the handful reserved for the owner (the event's one accountable coordinator) say so below. Two states shrink the page for everyone: an archived event rejects changes until it's unarchived, and demo events are read-only throughout. Here's every section, in the order it appears.

Identity and catalogueCopy Anchor Link

• Event name - what your Squad sees on the dashboard, invites, and emails. Renaming is safe: the invite link doesn't change.
• Known event - link (or unlink) this event to the catalogue. Linking switches on the catalogue surfaces - Guide tab, reviews, official info, artwork fallback - and never rewrites your own schedule, fields, or mode. See event types.
• Event imagery - one artwork image for cards and previews plus an optional lineup image; linked events fall back to the catalogue artwork.
• Event description - Markdown notes for your Squad at the top of the event page. Official catalogue info shows automatically alongside it on linked events.

ScheduleCopy Anchor Link

• Dates - event dates and sale dates, including overriding the catalogue defaults when you know better. Add another sale date puts a presale, a coach sale or a resale beside the main one. See dates.
• Event timezone - the shared anchor: every sale time renders in this timezone (with a UTC cross-check) for every member.

The two modesCopy Anchor Link

• Privacy - Open or Closed. Tighten any time, instantly; loosening back asks each member to confirm. The whole story is in Privacy.
• Tickets - named or transferable, switchable until someone records a ticket. The whole story is in Ticket modes.

Sale plansCopy Anchor Link

Named-ticket events only. Turn on sale plans to run more than one sale for the event - each with its own buying groups, its own date and its own answer to who is buying - and from then on this section lists your plans: rename, reorder, copy an arrangement, delete one that hasn't run a sale, link each to a sale date, set who's buying in it, cancel a sale, or turn the tools off again. Turning them on can't be undone in one way: the event keeps named tickets for good. The whole story is in Sale plans.

People, links, communityCopy Anchor Link

• Member permissions - whether each group's admin can manage their own group's members and helpers (on by default), or whether that stays with coordinators. On an event with sale plans it covers saying who in their group is buying or helping in that sale, too.
• Links - the chat places your Squad already uses (WhatsApp, Discord, Signal, Telegram) plus an optional Spotify playlist - and the invite link itself: if it's leaked, regenerate it and the old one stops working immediately.
• Community - attach the event to a community you admin, so its members can self-add; detach any time. (Attaching needs both hats: coordinator of the event and admin of the community.)
• Event permissions - see who runs the event. Any coordinator can promote a member to coordinator; taking coordinator rights away, and transferring ownership, are the owner's alone. This section stays available even on archived events, so a dormant event can always be handed over.

Data collectionCopy Anchor Link

• Custom data fields - the questions members answer: ten field shapes (text, pick-from-list, yes/no, email, currency, day of week, date, date/time, date range, URL), with per-field dials:
  • Required - needed to buy a ticket; readiness tracks only required fields. (What required means differs by ticket mode.)
  • Sensitive - shown on Closed events only, where new fields start sensitive until you say otherwise; a sensitive answer stays inside each buying group. Required and sensitive are independent choices. On Open events the dial appears when the event switches to Closed.
  • Allow multiple - for text and list fields.
  • Ticket-type preference - transferable events only: mark the one field (typically a pick-from-list, "seated or standing") whose answers power the demand tally on the Tickets board.
  • Used by a sale plan - a yes/no or pick-from-list question a plan uses to work out who's buying, or as its common choice, is named here with the plans that use it. Until they don't any more, you can't delete it, hide it, mark it sensitive or give it a different type, and you can't take away an answer a plan relies on. Renaming it and adding answers still work.
• Group size - the maximum members per buying group (named events only). It starts from your per-buyer ticket limit; clearing it removes the cap on joining, though readiness advice still works from the per-buyer limit.

LifecycleCopy Anchor Link

• Archive (owner - or the owner of the event's community) - puts the event to sleep: read-only, reminders and sale-day emails stop, and nobody can join. Unarchiving (owner) wakes it back up - with one honest caveat: pending ticket transfers were cancelled and live sale-day reveals revoked at archive time and don't come back.
• Step down as coordinator - hand back the reins and become a regular member. Everyone but the owner can; the owner transfers ownership first.
• Delete (owner) - the permanent one: groups, member data, invite links, and sale-day backup files go with it. You type the event's name to confirm, and it means it.