Creating an event
Three things are required at the time of posting. Everything else you can add later.
What's required
| Field | Notes | |
|---|---|---|
| Title | Required | What people see first. Write it like a flyer, not a filename. |
| Date | Required | Double-check this one — nothing stops you saving the wrong year. |
| Group | Required | Which of your groups is hosting. Picked automatically if you only have one. |
| Time | Optional | |
| Venue | Optional | |
| Description | Optional | |
| Cover image | Optional | |
| Categories | Optional | Helps the right people find it. Defaults to Social. |
| Capacity | Optional | Overall headcount. Ticket tiers have their own separate caps. |
| Age limits | Optional | Minimum age must be 18 or over if you set one. |
Publishing
Publish event puts it live immediately. Save as draft keeps it visible only to you and your co-admins.
The form saves as you type, so closing the app mid-way doesn't lose your work.
Run it with your team
Your events belong to your group, not to whoever happened to create them. Add co-admins and any of you can post and edit your group's events straight from your own profile — no shared login, no keeping track of which account made what.
Editing after it's live
Edit any of your group's events at any time, from any admin's profile. Prices and tiers can change while an event is live, but a tier that has already sold can't be removed — those tickets have to stay attached to something.
Cancelling or moving a date
If nothing has sold, the event is yours to handle: delete it outright, or save it back to draft to take it down while you sort the date out. Neither needs us.
Once tickets have sold, deleting is blocked — that record is the proof of what was paid and refunded. Change the date on the event itself and everyone keeps their ticket. If you're calling it off entirely, refund the buyers from your Stripe dashboard (see Refunds and cancellations) and message me so we can get word out to them.