Events Setup

The Events module lets you manage all kinds of events in your app: one-off dates, recurring meetings, multi-day conferences, online meetings or whole congresses with multiple sessions and speakers. Registrations, waitlists, tickets and reminders are built-in.

Automatic Firebase setup

The Firebase setup (security rules, indexes, cloud functions) happens automatically when you publish your app. When activating the Events module you don’t have to deal with Firebase yourself.

Overview

Events

Create dates with date, time, venue, description and image.

Registrations

Participants register or cancel directly inside the app.

Waitlist

Promote automatically when full events open up.

Tickets & Payment

Paid events with ticket types and tax.

Recurrence

Daily, weekly or monthly events in one step.

Multiple views

List, grid, calendar, agenda, map, carousel and tiles.

Speakers & Sessions

Map conferences with speakers and multiple sessions.

Push notifications

Reminders, registration confirmations, waitlist updates.

---

Activation at a glance

Property	Value
Activation type	Guided setup with five steps
Automatic defaults	Yes - the module is ready to go
Required dependency	Firebase (for data storage)
Recommended optional modules	Notifications, Maps, Email, Membership
Path	App Builder Tools → Modules & Features → Events → Activate

What does “sensible defaults” mean?

You can simply click through all five setup steps without changing anything. The module is then active with good default values. Every value can be tuned later in the Events Editor.

---

Setup flow

The setup consists of five steps:

1. Introduction - Overview of what the Events module can do

2. Choose features - Which main features you want to enable right away

3. Default view - Which displays your users see

4. Permissions - Who is allowed to create events and do they need approval?

5. Design - Use the global app design for events

---

The setup steps in detail

Step 1: Introduction

The first step shows you everything that’s in the module:

Feature	Description
Create events	Dates with date, venue, description and image
Manage registrations	Attendee list, CSV export, waitlist
Tickets & Payment	Paid events with various ticket types
Recurrence	Dates that recur daily, weekly or monthly
Multi-day events	Conferences or festivals over several days
Speakers & Sessions	Conferences with program and speakers
Custom registration fields	Extra info like diet, t-shirt size, vegan yes/no
Bookmarks & calendar export	Users save events or add them to Apple/Google Calendar
Reminders	Push notifications 24 hours and 7 days in advance

You don’t have to choose anything

Step 1 is purely informational. Tap Next to continue.

---

Step 2: Choose features

In this step you decide which four main features are active immediately:

Feature	Default	Good for
Cover image	On	Every event has an image at the top
Registrations (RSVP)	On	Attendees register inside the app
Tickets	Off	Activate when events should cost money
Recurrence	On	Dates that recur regularly

Extendable later

In the Events Editor you can turn on or off more than 30 additional features after activation - like gallery, speakers, sessions, waitlists, online events, bookmarks, calendar export or reminders.

---

Step 3: Default view

Here you choose which displays users can see. Seven displays are available:

Display	Description	Default
List	Stacked, classic	On
Grid	Several cards next to each other	On
Calendar	Monthly, weekly or daily view	On
Agenda	Chronologically grouped by day	On
Map	Geographical display (needs the Maps module)	Off
Carousel	Big image, swipe through	On
Tiles	Big preview tiles	On

Map view

The map view also needs the active Maps module. As long as that is not active, this view stays hidden in the app.

---

Step 4: Permissions

This step decides who is allowed to create events and how the approval workflow works.

Who can create?

Mode	Meaning
Admins only	Only people with admin rights create events. Default.
Logged in users	Everyone with an account is allowed
Verified users	Only people with a confirmed email address

Approval workflow

Mode	Meaning
Off	Events are visible immediately
Pre-approval	Events need approval by an admin first
Hybrid	Trusted users publish directly, others need approval. Default.

Recommendation

Leave the defaults “Admins only” and “Hybrid” in place to begin with. Once your app’s structure has settled, you can allow other people to create events at any time.

---

Step 5: Design

In the last step the module takes over the global design of your app. That means colors, fonts and corner radii come from the Theme Suite.

After tapping Finish setup the module is active and you land directly inside the Events Editor where you can fine-tune things at any time.

What happens at finish?

At the end a few default categories and example custom field templates are created automatically so that you can hit the ground running.

---

What gets set up in the background?

When you publish your app the platform sets up everything necessary automatically. You don’t need to take care of it - but for a complete picture here’s an overview:

Database areas (Firestore Collections)

Area	Content
events	All events
events/{id}/registrations	Registrations per event
events/{id}/tickets	Bought tickets per event
events/{id}/checkins	Check-in data at the door
eventCategories	Categories
eventTemplates	Templates
eventVenues	Venues
events_analytics_events	Usage stats for analytics

Automatic server functions (Cloud Functions)

Three bundles ensure that push notifications, tickets and emails work automatically:

Bundle	Purpose
Events: Push notifications	Sends push notifications on creation, update, cancellation, registration, waitlist promotion, ticket purchase, reminder and report
Events: Tickets	Issues tickets after payment, handles check-ins, manages refunds, clears expired waitlist seats
Events: Email	Sends registration confirmations, ticket PDFs, cancellations, reminders and refund mails

Security rules (Firestore & Storage)

Special rules make sure:

• Only matching users can see events (according to scope and visibility).
• Registrations can only be created by logged-in users and only edited by the organizer / admin.
• Images in the gallery are only accessible by authorized users.

---

Permissions in the app

Who	What they can do
All users	View published events (matching their visibility)
Logged-in users	Register, bookmark, export to calendar
With “create” permission	Create their own events (per permission mode)
Organizers	Edit own events, see registrations
Moderators / Admins	Edit, approve, reject all events, handle reports

---

Dependencies

Module	Type	Description
Firebase	Required	Needed for storing all event data
Notifications	Recommended	So push messages actually arrive
Maps	Optional	Only needed if you want to use the map view
Email	Optional	For registration and ticket emails
Membership	Optional	For discounted tickets or member-only events
Payment	Optional	Will be wired in automatically when you enable tickets

---

First steps after activation

1. Create categories - Open /admin/events/categories and create your own categories (like “Workshop”, “Concert”, “Members meeting”).

2. Add venues - Open /admin/events/venues and enter venues you use often. This saves a lot of time when creating individual events later.

3. Create the first event - Open /admin/events/create or tap Create event in the dashboard.

4. Check the default view - In the editor under View → Default view decide what users see when opening the events page.

5. Configure push notifications - In the editor under Behavior decide for which triggers push notifications are sent.

6. Tune the home page - In the editor under Home activate the sections you want (Upcoming, This Week, Popular, Free etc.).

---

Tips

Defaults are good enough

You can simply click through all five setup steps without changing anything. The shipped defaults work right away and you can adjust everything later in the editor.

Create templates early

If you regularly publish similar events, create a few templates at the start. When creating new events you just pick the matching template and save yourself the typing.

Maps module only when needed

Only enable the map view when your events are location-based and users actually benefit from it. Otherwise leave it off - this saves bandwidth and load time.

Don’t forget privacy

In the editor under Behavior → Privacy / Retention you set when personal data from registrations is automatically removed. Default is 90 days after the event ended.

---

Next steps

Events Editor All tabs and settings in detail

Features Over 30 toggles in detail

Permissions Approval workflow and auto-hide

Home Events sections on the home page