Introduction
Use this guide when you already know the Program-related task you need to complete and want a clear operational path.
Programs are most useful when your organization is not simply promoting one event, but is presenting a broader initiative made up of related events. That could mean a training series, a seasonal program, a learning cohort, or a conference-style experience where supporters should first understand the overall offering and then choose one or more sessions.
This page focuses on the most common Program setup and management tasks.
When to use this page
Use this page when you need to:
- build a supporter-facing page for a cohort, series, or multi-session initiative
- protect a Program behind a password
- expose filters that help visitors browse related events
- support multi-event selection and checkout
- understand how discount codes apply during Program checkout
- review Program-level and Event-level registrations
Before you start
Before you configure a Program, confirm a few things first:
- this experience is truly broader than one Event
- the related Events already exist or are close to ready
- your team knows whether supporters should register for one Event at a time or several in one flow
- the Program page needs to help people discover options, not just land on one registration form
A Program usually adds value when it makes the public journey clearer. If it is only adding structure for staff but not helping supporters understand the initiative, it may be worth checking whether a simple Event would be enough.
Build a cohort-style registration page
Use this workflow when supporters should understand a broader initiative first and then choose from related Events underneath it.
This works especially well for:
- workshop series
- training cohorts
- seasonal classes
- mentoring or leadership programs
- multi-session learning experiences
- conferences or summits with selectable sessions
Step 1 — Create the Program
Start by creating the Program record.
Use the Program to explain the broader initiative, not just the logistics of one session.
At a minimum, make sure the Program page gives visitors enough context to understand:
- what the initiative is
- who it is for
- why it matters
- whether they should expect one Event or several related options
This is what makes the Program page feel like a guided entry point instead of just a grouping container.
Step 2 — Publish the related Events
Make sure the Events that belong in the Program are actually ready to appear publicly where appropriate.
That usually means checking:
- titles and descriptions
- dates and times
- visibility
- registration readiness
- event-level details that a visitor would need before selecting that Event
A Program is only as clear as the Events it contains. If the Program page looks polished but the underlying Events feel incomplete or inconsistent, the public experience becomes confusing.
Step 3 — Assign each Event to the Program
Attach each relevant Event to the Program from the Event side.
This is what allows the Program page to become a real discovery experience with actual selectable options underneath it.
As you assign Events, check whether they belong together from the supporter’s point of view, not just from the organization’s point of view.
For example, Events might be related internally because the same team runs them, but that does not always mean supporters should experience them as one Program.
Step 4 — Turn on Allow multi-event registration
Enable Allow multi-event registration when supporters should be able to select more than one Event in the same journey.
This is often useful when:
- people commonly attend several sessions
- the Program is meant to feel like one coordinated experience
- staff want to reduce friction by letting someone make multiple selections in one checkout flow
Be more cautious when:
- each Event needs a separate decision or approval
- the Events are related but not intended to be purchased or selected together
- staff want to keep each Event’s registration path separate and simple
Step 5 — Review the public Program page
Once the Program and related Events are connected, review the public page from a supporter’s perspective.
Make sure the page does these jobs well:
- explains the larger initiative clearly
- shows the related Events in a way that makes sense
- makes it obvious what can be selected
- supports either one-event or multi-event selection cleanly
- does not feel overloaded or unclear
Good practice
Review the page on both desktop and mobile if you can. Program pages often get shared through email, social links, direct outreach, or partner referrals, so supporters may arrive without much context.
Password-protect a Program
Use password protection when the Program should not be openly browsable by the public but still needs a supporter-facing landing page and registration experience.
This is often useful for:
- invite-only donor education series
- member-only training programs
- partner-only sessions
- early-access or pilot cohorts
- programs that should be shared only with a defined audience
Step 1 — Open the Program
Go to the Program record in the dashboard.
Step 2 — Set Visibility to Password protected
Choose the password-protected visibility option.
Step 3 — Enter an access password
Add the password visitors will need in order to unlock the Program page.
Step 4 — Save and test the flow
Save the Program, then open the public page and test the unlock experience yourself.
Do not assume it is working correctly just because the setting saved. Password-protected experiences are worth testing end to end, especially before they are shared with donors, partners, or registrants.
What supporters will experience
Visitors will need to enter the password before they can view the Program page or begin checkout.
Good practice
Make sure the team sharing the Program understands:
- who should receive the password
- how the password will be communicated
- whether the Program should also remain hidden from broader promotion
A password-protected Program is best when it feels intentionally exclusive, not accidentally difficult.
Turn on public filters
Use public filters when the Program includes enough Events that supporters need help narrowing down what is relevant to them.
Available filters may include:
- date
- hosts
- event types
- tags
Only enabled filters appear on the public Program page.
Step 1 — Open Filters & Registration
Go to the Program’s filter and registration settings.
Step 2 — Enable only the filters that will genuinely help supporters
Turn on the filters that make the page easier to use.
Good candidates are filters that help someone answer a real decision-making question, such as:
- Which date works for me?
- Which facilitator or host do I want?
- Which kind of session is relevant?
- Which topic or tag best matches what I need?
Step 3 — Save and review the public page
After saving, review the public Program page and test whether the filters make the experience clearer.
When filters help
Filters are especially useful when the Program includes:
- many related sessions
- multiple topics
- more than one facilitator or host
- several dates spread over time
- a public-facing catalog-style experience
When to keep it simple
Avoid turning on filters that expose internal distinctions supporters do not actually care about.
Too many filters can make the Program page feel like a database rather than a guided supporter journey.
Example
A public education Program may benefit from filters for date and topic.
A small donor education series with only a few sessions may not need filters at all.
Apply a program discount code
Use this when supporters should be able to receive a discount during Program checkout.
Program checkout supports tenant discount codes. During checkout, supporters can enter the code and the platform recalculates the total before payment.
What this is useful for
Discount codes can support things like:
- early-bird pricing
- partner offers
- member benefits
- staff-issued accommodation codes
- special promotional campaigns
How it works
The discount applies to the Program checkout total for the selected Events, based on the code rules currently configured.
That means the effect of the code depends on:
- which Events the supporter selected
- how the discount code was configured
- whether the code is valid and active at checkout
Good practice
Before promoting a discount code widely, test it through the full Program checkout flow.
Confirm:
- the code is accepted
- the total recalculates as expected
- the resulting price matches your intent
- the code behaves correctly when several Events are selected
The best time to catch a discount issue is before supporters start using it.
Review program registrations
Programs usually create two different reporting and operational views:
- a broader Program-level registration view
- the Event-level registrations underneath it
Understanding the difference helps staff review the right thing in the right place.
Program Registrations
Use Program Registrations when you want the broader checkout-level view.
This is the right place when the question is about:
- one combined registration journey
- who registered through the Program as a whole
- checkout-level patterns
- broader participation across the initiative
Registrations
Use Registrations when the question is really about one underlying Event.
This is the right place when you need to review:
- event-specific attendance
- one session’s registration count
- one Event’s waitlist or capacity behavior
- one session’s operational issues
- event-level follow-up needs
Broadcasts
Use Broadcasts to review communication history tied to the Program.
This is especially useful when the message applies to the broader initiative rather than to one single Event.
Examples include:
- welcome to the series
- overall schedule updates
- program-wide reminders
- initiative-level follow-up
Good practice
Before reviewing registrations, ask:
Is this a Program-level question or an Event-level question?
That one habit helps staff avoid confusion when a Program contains multiple Events with their own separate operational realities.
Tips and notes
Programs are strongest when they clarify the supporter journey. If the page feels more complex after adding a Program, revisit whether the structure is actually helping.
Multi-event registration should be an intentional public-experience decision, not just a feature toggle.
A Program page can look complete while the underlying Events are still inconsistent. Always review both the Program and the attached Events before launch.
Turning on too many filters can make a Program feel harder to use, not easier.