Introduction
Events can be simple listings, classes, workshops, webinars, scheduled programs, ticketed events, or pass-based access. Event type controls which tabs and workflows matter.
Use Cases
- Promote upcoming classes, workshops, performances, webinars, and other one-off or recurring events.
- Let people register or buy tickets and passes for events that require them.
Supported fields
Basics
- Section label
- Optional. A short label that can appear above or beside the events heading. It is often decorative, but it can also carry a proof point, qualifier, or small trust signal.
- Title
- Recommended. The main heading for the events section. It tells visitors what this part of the page is about before they scan the items underneath.
- Intro
- Optional. Supporting text for the events heading. It gives context before visitors reach the cards, list, gallery, or form below.
- Icon
- Optional. An icon for events templates that include a small visual marker. It can help establish the section theme without requiring a full image.
- Secondary title
- Optional. A supporting heading used when an event detail page needs to show more events after the main event.
- Time format
- Optional site preference. Controls whether event times are shown in 12-hour or 24-hour style when event templates support it.
Events
- Events
- Multiple events per site. Each event is a reusable record that can appear in the event list, have its own detail page, sell tickets, accept class bookings, or unlock course content.
- Event type
- One type per event. Chooses the event workflow: meetup, workshop/class, ongoing access, event with schedule, special occasion, webinar/online event, or online course.
- Enabled
- One on/off setting per event. Controls whether the event is included in public event data.
- Show on homepage
- One on/off setting per event. Controls whether the event appears in homepage event sections while still allowing it to exist elsewhere.
- Categories and levels
- Optional; multiple class labels. Reusable labels for class-style events. Levels and categories help visitors filter recurring schedules when the site offers many classes.
Event Basics
- Event name
- Required for each event. The public title of the event. It becomes the event card title, detail page heading, ticket email subject/context, class booking label, and event URL.
- Description
- Recommended for each event. Short event copy for cards and the top of the detail page. It should explain why someone would attend, buy, book, or keep reading.
- Start date and end date
- Required for dated events; optional for ongoing access. The date range for one-off and scheduled events. Recurring events use the start date as the anchor for generated occurrences.
- Start time and end time
- Recommended for dated events. The default time window for the event. Recurring events can override this with multiple time slots.
- Venue or location
- Recommended. The public place label for the event. When a linked location or custom address is available, event detail pages can use that for maps; otherwise the venue text is shown as the readable place.
- Recurring event
- One on/off setting for supported event types. Turns a dated event into a repeated schedule. When enabled, the Recurrence tab controls the pattern and future occurrences.
- Capacity
- Optional per event. The total attendee limit for the event. Ticket availability and class booking availability can both use this value.
- Current bookings
- Optional manual count. A starting attendance count for bookings or sales that happened outside Flax.
- Enable waitlist
- Optional per dated or recurring event. Allows class-style booking to accept waitlist entries after capacity is full.
- Allow booking for future events
- One on/off setting for recurring events. Controls whether visitors can book any generated future occurrence or only the next upcoming occurrence.
- Course access
- Optional for online course events. Links an event to one or more article course sections. Purchased or booked access can then point customers toward course lessons.
- Has agenda
- One on/off setting for agenda-capable events. Adds the Agenda tab for multi-day, multi-track, or scheduled programs.
- Has tickets
- One on/off setting for ticket-capable events. Adds the Tickets tab and allows the event detail page to sell or display ticket types.
- Icon
- Optional per event. A compact visual marker for event cards, event type layouts, and lightweight schedule views.
Countdown
- Countdown title
- Optional. A short heading shown near countdown templates instead of repeating the event name exactly.
Recurrence
- Frequency
- One frequency per recurring event. Defines whether the event repeats daily, daily on selected days, weekly, monthly, or yearly.
- Repeat every
- One interval per recurring event. Sets the spacing of the recurrence, such as every week, every two weeks, or every month.
- Run on these days
- Optional day selection for selected-day daily rules. Limits a daily recurrence to specific weekdays.
- Time slots
- Optional; multiple slots per recurring day. Creates more than one bookable or displayed time on the same recurring date. If no slots are added, the event uses the start/end time from Event Basics.
- End date
- Optional. Stops the recurrence after a specific date.
- Exception dates
- Optional; multiple skipped dates. Removes specific dates from the recurrence pattern without changing the overall rule.
- Upcoming occurrences preview
- Generated preview. Shows the next generated dates and times from the current start date, recurrence rule, time slots, and exceptions.
Agenda
- Agenda days
- Multiple days per agenda. Top-level schedule days for the event.
- Day name
- Optional per day. A readable label such as Day 1, Opening Day, Workshop Day, or Saturday.
- Date
- Recommended per agenda day. The calendar date for this schedule day.
- Tracks
- Multiple tracks per day. Tracks group sessions that happen in parallel or in separate rooms, stages, themes, or streams.
- Sessions
- Multiple sessions per track. Individual agenda items with title, speaker, and start/end time.
- Session description
- Optional per session when present. Extra explanation for a session, such as topic, format, or outcome.
Event Content
- Content blocks
- Optional; multiple blocks per event. Reusable page sections for deeper event information: text, images, highlights, buttons, explanations, and supporting media.
- Block images
- Optional; multiple images across blocks. Images inside content blocks can supplement or replace the event image gallery when the page needs visual explanation.
Tickets
- Ticket types
- Multiple tickets per event. The purchase or registration options for this event.
- Name
- Required for each ticket. The public ticket label shown to customers before purchase and in confirmation emails.
- Description
- Optional per ticket. Explains what the ticket includes or how it differs from other tickets.
- Price
- Optional; required for online paid checkout. The ticket price shown on the event page and used for checkout when no external link is provided.
- Currency
- Optional per ticket; ISO currency code. The currency used for ticket display and checkout.
- Quantity
- Optional ticket limit. Caps how many of this ticket type can be sold online.
- Available until
- Optional ticket deadline. Hides or blocks a ticket after a specific date and time.
- External link
- Optional per ticket. Sends visitors to another ticketing service instead of Flax checkout for that ticket.
- Sold out
- One on/off setting per ticket. Manually marks a ticket unavailable while keeping it visible as sold out.
- Door price only
- One on/off setting per ticket. Shows the ticket or price for reference but prevents online purchase.
- Payment sync IDs
- Managed automatically when payments are connected. Links online paid tickets to payment-provider products and prices after event payment sync.
Images
- Images
- Multiple images per event. Photos or graphics that visually represent the event.
- Image focus
- Optional per image. Controls which part of an image remains visible when cards or hero layouts crop it.
Passes
- Passes section label
- Optional. A small label for the passes display section.
- Passes heading
- Recommended when selling passes. The main heading for the pass sales section.
- Passes intro
- Optional. Supporting copy for how passes work and who they are for.
- Passes icon
- Optional. A small visual marker for pass sales templates.
- Pass name
- Required for each pass. The public name of the credit pack, subscription, membership, or access product.
- Description
- Optional per pass. Explains what the pass includes, how it renews or expires, and any restrictions.
- Icon
- Optional per pass. A compact visual marker for pass cards.
- Pass type
- One type per pass. Chooses between a one-time credit pass and a recurring subscription.
- Credits
- Required for credit passes; optional for subscriptions. The number of class credits included. For subscriptions, zero can mean unlimited credits for the billing period.
- Validity
- Required for credit passes. How long a one-time pass remains usable after purchase.
- Billing interval
- Required for subscriptions. How often a subscription renews, such as monthly, weekly, yearly, or every N periods.
- Price
- Required for paid passes. The amount charged for the pass or subscription.
- Allowed events
- Optional; multiple events per pass. Restricts a pass to selected recurring events. If no events are selected, the pass can apply broadly.
- Mixed credits
- Optional; multiple event allowances. Lets one pass contain different credit amounts for different events.
- Pass enabled
- One on/off setting per pass. Controls whether the pass is available for sale and use in pass selection flows.
- Featured
- One on/off setting per pass. Marks a pass as promoted in pass card layouts.
- Sold out
- Optional per pass when configured. Prevents a pass from being sold while preserving the pass record.
- Payment sync IDs
- Managed automatically when payments are connected. Links paid passes and subscriptions to payment-provider products and prices.
Payments
- Inherit from site
- One on/off setting. Uses the site payment setup as the base configuration for event checkout.
- Disabled methods
- Optional; multiple methods can be disabled. Turns off selected global payment methods for event checkout while leaving them available elsewhere.
- Disabled fees
- Optional; multiple fees can be disabled. Turns off selected global fees for event checkout while leaving them available for other checkout flows.
- Stripe sync
- Automatic when Stripe is enabled for Events. Syncs online paid tickets, credit passes, and subscriptions to payment-provider products and prices.
Checkout Form
- Checkout form
- One active form for event tickets. The form visitors complete when buying event tickets through Flax checkout.
- Questions
- Multiple questions per checkout form. Custom fields collected from the ticket buyer.
- Required
- One on/off setting per question. Controls whether a customer must answer a question before checkout can continue.
- Field type
- One type per question. Controls the input style and how the answer is captured: text, email, phone, select, checkbox, textarea, and similar form controls.
- Receiver email
- Optional per form. The merchant destination for ticket checkout notifications when a specific recipient is set.
- Auto-confirm orders
- Optional event checkout setting. Controls whether non-Stripe event orders are treated as confirmed immediately instead of waiting for staff review.
- Confirmation notes
- Optional. Customer-facing copy included after an event order is confirmed.
Settings
- Event catalog display
- One events catalog per site; multiple display sections possible. The Events content is one shared catalog, but the site can display it through the main Events section, event detail pages, class schedules, and a passes-focused section.
- Enabled
- One on/off setting. Controls whether the events section is rendered on the published site.
- Show on homepage
- One on/off setting. Controls whether events appears on the homepage. Some content can still be used by detail pages, forms, checkout, bookings, or generated pages even when the homepage block is hidden.
- Display name
- Optional. The label used when the events section needs a short name outside its full heading.
Preview
Events examples
These examples use Flax templates with sample content. The selected template controls the final appearance on your site.
Loading examples…