/ to search
Documentation Programs

Programs

Programs Reference

Browse tenant guides generated directly from the Markdown files in docs/tenant.

Overview

This reference lists the confirmed staff-facing areas, settings, public behaviors, and communication surfaces for Programs.

Use this page when you need a quick reminder of:

  • where Program work happens
  • which settings exist on the Program record
  • how the public Program experience behaves
  • how Program-level behavior differs from Event-level operations

Staff-facing areas

The Program area includes:

  • Programs resource
  • Program Registrations relation
  • Registrations relation
  • Broadcasts relation

These surfaces support both the broader initiative-level view and the event-level activity that sits underneath it.

Program settings

Confirmed Program settings include:

  • title, slug, short description, long description
  • team assignment
  • starts at, ends at, timezone
  • status: draft, published, archived
  • visibility: public, password protected, hidden
  • public filters by date, hosts, event types, and tags
  • multi-event registration toggle
  • public marketing consent settings
  • default tracking source and subsource
  • banner image
  • search-engine indexing toggle
  • contact name, email, phone, website

Setting guidance

Title, slug, and descriptions

Used to define the Program publicly and explain the broader initiative.

Team assignment

Used when the Program should be managed operationally by a specific team.

Starts at, ends at, timezone

Used to frame the Program itself, even though the individual events underneath it still manage their own event-level schedules.

Status

Controls the Program lifecycle, such as draft, published, or archived.

Visibility

Controls whether the Program is public, hidden, or password protected.

Public filters

Allow the Program page to function as a discovery layer for related events.

Multi-event registration toggle

Controls whether supporters can select multiple eligible events in one registration flow.

Public marketing consent settings

Affect public consent capture where applicable in the Program flow.

Default tracking source and subsource

Support attribution and channel tracking for Program-level public traffic.

Banner image

Helps shape the visual identity of the Program page.

Search-engine indexing toggle

Controls whether the Program page should be indexable where supported.

Contact information

Provides a public contact reference for the Program experience.

Public Program behavior

Confirmed public behavior includes:

  • hidden Programs return a public 404
  • password-protected Programs show an unlock page
  • only eligible visible events appear on the Program page
  • full events without waitlist support may be excluded from selection
  • multi-event checkout uses a cart-style flow
  • checkout has payment-status polling and thank-you pages

Public behavior notes

Hidden Programs

A hidden Program is not available publicly and returns a public 404.

Password-protected Programs

A password-protected Program shows an unlock page before the supporter can view the Program content or start checkout.

Eligible visible events only

The public Program page does not simply show every related event record. It shows the events that are eligible to appear publicly under the Program.

Full events without waitlist support

If an event is full and does not support waitlist behavior, it may be excluded from selection.

Multi-event checkout

When multi-event registration is enabled, the Program checkout uses a cart-style selection flow rather than a single-event registration pattern.

Payment-status polling and thank-you pages

The checkout flow includes post-payment status handling and thank-you behavior.

Program Registrations

Program Registrations represent checkout-level or Program-level registration activity.

Use this view when the staff question is about the broader Program journey rather than one specific event underneath it.

Registrations

The Registrations relation gives visibility into the related event registrations beneath the Program.

Use this when the staff question is really about one event’s operational details.

Examples include:

  • event-specific attendance
  • one event’s registration volume
  • one event’s waitlist behavior
  • one session’s follow-up needs

Broadcasts

Program broadcasts include:

  • subject
  • preview text
  • status
  • recipients
  • sent and failed counts
  • queued and sent timestamps

Program-level broadcasts are useful when the message applies to the broader initiative rather than one specific event.

Operational notes

  • Programs are only available when the tenant’s programs module is enabled.
  • Events are attached to Programs from the event record, not by adding them directly inside the Program form.
  • Programs organize related events, but do not replace event-level operations.
  • Attendance, waitlists, event-specific reminders, and other occurrence-level workflows still live on the individual events.

Notes

  • Programs are best used when the supporter journey begins with understanding a broader initiative.
  • Public filters are most useful when the Program contains enough related events to make discovery meaningful.
  • Multi-event registration changes the public journey and should be enabled intentionally.