Events Webinars and Coaching

New in version 1.0.04

Events in BricksMembers are for scheduled member experiences: live classes, webinars, coaching calls, cohort sessions, office hours, workshops, accountability calls, and community meetups. If your membership or course has anything that happens at a specific time, the Events module gives you a structured way to manage it without forcing you to bolt together separate calendar, access-control, payment tools, and page-builder tools.

The important part is that Events are not just calendar entries. They can be targeted to the right members, connected to groups and team licenses or offers, displayed in Bricks, protected by access rules, and optionally connected to meeting providers such as Zoom, Google Meet, or Microsoft Teams. That makes them useful for both simple “join this webinar” setups and more advanced learning businesses where different cohorts, groups, or customers should see different sessions.

When to Use Events

Use Events when the thing you are creating has a scheduled start time and a member-facing experience around that time. A normal lesson page is still the right choice for evergreen content. An Event is the right choice when people need to register, attend, join a call, add something to their calendar, or see a schedule of upcoming sessions.

• Live classes for a cohort-based course
• Webinars for launches, onboarding, demos, or training
• Group coaching calls for paying members or specific teams
• Office hours where members can ask questions
• Community sessions such as meetups, workshops, or Q&A calls
• Private group events that only a group owner or group members should see

If you only need to show a static date on a lesson page, you probably do not need an Event. If members should interact with a scheduled session, register for it, join it, or see it in a calendar, use the Events module.

Enable the Events Module

1. Go to BricksMembers → Modules.
2. Enable Events.
3. Open BricksMembers → Events.

After the module is active, BricksMembers adds the Events admin surface and registers the event runtime used by Bricks elements, dynamic tags, Bricks conditions, provider connections, registrations, and calendar views.

Events are built for larger calendars too. BricksMembers keeps event details, targets, registrations, and attendance in dedicated indexed tables, and frontend event reads reuse request-level caches so calendars, join buttons, and dynamic tags do not repeat the same database work over and over.

Plan Your Event Before You Create It

Before clicking “Create Event,” decide what kind of session you are actually running. This keeps your setup clean and prevents you from mixing access rules, registration behavior, and meeting links later.

• Who should see the event? Everyone, logged-in members, a specific user level, a group, an enrollment, a role, a user, or customers with a certain offer key?
• Should people register? Some events should accept registrations and capacity limits; others are just scheduled join links for eligible members.
• Do you need a waitlist? This is useful for workshops, coaching calls, and live sessions with limited seats.
• Is there a payment or upsell path? Events can use offer keys when purchase access or upgrade messaging should apply.
• Will the meeting be provider-managed? If you use Zoom, Google Meet, or Microsoft Teams, connect the provider first. If not, use a manual join URL.

A good rule is to start with the audience. If the audience is wrong, everything else feels wrong: the event appears in the wrong calendar, the wrong users see the join button, and your automations or follow-up workflows become harder to reason about.

Create Your First Event

1. Open BricksMembers → Events.
2. Open the Events tab.
3. Click Create Event.
4. Enter the title and description. Use a title members will understand, such as “May Coaching Call” or “Cohort 3 Live Workshop.”
5. Choose the event type and status.
6. Set the start time, end time, timezone, and capacity.
7. Choose whether registration and waitlist are enabled.
8. Choose the access mode: public, members, or targeted access.
9. Add targets when the event should be limited to a level, group, enrollment, role, user, or offer key.
10. Add a required offer key when a purchase should be required before registration.
11. Add an upsell offer key when your Bricks template should show an upgrade or purchase button.
12. Save the event.

For a first setup, keep the event simple. Create one public or member-only session, confirm that it appears on the frontend, then add more advanced targeting once the basic flow is working.

Connect Zoom, Google Meet, or Microsoft Teams

Provider connections let BricksMembers create or manage meeting artifacts without exposing private credentials to normal event editors. This is useful when your team runs many sessions and you want meeting links to be handled consistently.

1. Open the Provider Connections tab.
2. Click Add Connection.
3. Select the provider.
4. Enter the required credentials for that provider.
5. Save the connection.
6. Edit an event and select the saved provider connection.

You do not have to use a provider connection for every event. Manual events are still valid. Leave the provider empty and enter a direct join URL when you already have a meeting link, when the session happens outside a supported provider, or when you want to handle the link manually.

Control Who Can See, Register, and Join

Events use access state to decide what a visitor should see. A user might be able to view the event listing, register for the event, join the event, join the waitlist, or see an upgrade button. Those states are separate because real membership sites often need more than a single yes/no rule.

• Public events can be used for open webinars, launches, and discovery sessions.
• Member events are useful for logged-in community calls and customer sessions.
• Targeted events are best for specific levels, groups, enrollments, roles, users, or offer keys.
• Offer-gated events help you connect scheduled sessions to paid products, upgrades, or group-license offers.

If you are running a paid coaching program, for example, the event can be visible only to the right members, registration can be limited by capacity, and the join button can appear only when the event is close enough or when the user has the right access state.

Show Events in Bricks Builder

BricksMembers is designed to let Bricks handle the frontend layout. Since version 1.1.1, you can use native Bricks post query loops for brm_event event lists, native user query loops for event attendees, colon dynamic tags such as {brm_event:title} and {brm_event:join_url}, and Events conditions to show the right buttons at the right time.

A typical event card in Bricks might include the event title, date, time, short description, registration button, waitlist button, join button, and calendar links. You can build that card with normal Bricks elements and then use Events dynamic tags and conditions to make it respond to the current event and current user.

Use the Event Calendar Element

Use the BRM Event Calendar element when you want a full discovery surface instead of a custom query-loop list. The calendar supports month, week, list, and year views, optional visitor view switching, event type and group filters, accessible-only filtering, hide-full filtering, timezone display modes, registration and cancellation buttons, join links, ICS downloads, and Google Calendar links.

When someone clicks an event in the calendar, you can choose what happens next. The default built-in detail popup uses the calendar feed and keeps the standard register, cancel, join, ICS, and Google Calendar actions. You can also send the click to the single event page, or open a Bricks Popup template. Popup templates receive the clicked brm_event post as context, so you can design the popup in Bricks with Event dynamic tags and conditions while keeping registration and join actions owned by BricksMembers.

The week view is a timed schedule. Events are positioned by their start and end times, overlapping sessions share columns, and long or cross-day sessions are clipped to the current day’s visible grid. Use it for live class schedules, cohort calendars, webinar weeks, and coaching calendars where time placement matters.

For most sites, the simplest setup is to create one page called “Events” or “Live Sessions,” add the Event Calendar element, and then use filters to decide what visitors can browse. If your membership has several programs or cohorts, you can create separate pages for different audiences and configure each calendar differently.

A Practical Setup Example

Imagine you sell a course with a monthly group coaching call. You want students to see upcoming calls, register while seats are available, join the Zoom call when it starts, and add the session to their calendar.

1. Create a new event called “Monthly Coaching Call.”
2. Set the start and end time in the correct timezone.
3. Enable registration and set a capacity if the call has limited seats.
4. Target the event to the course level or enrollment that should unlock it.
5. Select your Zoom provider connection or paste a manual join URL.
6. Add an Event Calendar or event query loop to the member dashboard.
7. Use Events conditions so the registration, waitlist, join, or upgrade button appears only when it makes sense.

This gives students one clear place to find the next call. They do not need to search email threads, remember a Zoom link, or ask support where the schedule lives.

Who Can Create Events?

Admins can give trusted roles the Manage events, Create events, or Create group events capability under BricksMembers → Roles & Permissions. User levels control event access and targeting, but they do not automatically grant access to the Events admin screen.

For group-owner event creation, use the scoped group capability. BricksMembers forces the event to the owner’s group and does not expose site-wide provider connections unless another capability allows that. This keeps group events useful without giving group owners more access than they should have.

Common Mistakes to Avoid

• Using one public event for every audience. If different members should see different sessions, use targets.
• Forgetting the timezone. Always check the timezone for live classes and international communities.
• Showing every button all the time. Use Events conditions so users only see actions they can actually take.
• Putting provider credentials in normal content. Use provider connections when the integration should own the meeting setup.
• Skipping a test registration. Test as an eligible member and as an ineligible visitor before announcing the event.

A Good Default Workflow

1. Enable Events.
2. Create one simple member-only event.
3. Add the Event Calendar to a dashboard or events page.
4. Confirm the event appears for the right users.
5. Test registration, waitlist, cancellation, join links, and calendar links.
6. Add provider connections and offer gates only after the basic flow is working.

That workflow keeps the first launch manageable. Once the first event behaves correctly, you can expand into provider-managed sessions, group-owner events, paid webinars, advanced Bricks templates, and automation follow-ups without rebuilding the whole setup.