Event
Event pages are used to gather RSVPs to Events managed with Solidarity Tech. You must create the Event before you can set up the event page. The form associated with the Page will automatically include a checkbox for each of the future event sessions supporters can RSVP to.
](https://files.readme.io/89a1a94-image.png)
View an example event page here
A form submission with a checkbox selected for an event session is equivalent to the supporter being marked as a Yes RSVP by a Team Member.
Event pages can also sell paid tickets instead of collecting free RSVPs. See Selling Tickets below.
Email confirmation is disabled for this page type. Email confirmations should be configured at the Event level, so that all People RSVPing to the event - whether from a phonebank or the event page - will receive the same email confirmation with a calendar invite.
Event Page Settings
When editing an event page in the dashboard, you'll find an Event Page Settings section under the Basics tab. These settings control behavior specific to event pages.
Hide Address Until RSVP
For in-person events, you can hide the full street address on the public event page. When enabled, visitors see the general area (e.g. "Oakland, CA") along with "RSVP to see address" instead of the full address.
This is useful when you don't want the exact location publicly visible, for example, events at private residences or locations with security concerns. People still need to RSVP to get the address.
To enable:
- Open the event page in the dashboard
- Go to Basics
- Scroll to Event Page Settings
- Toggle Hide Address Until RSVP
Where the address is hidden:
- The public event page shows "City, State" with "RSVP to see address"
- Event cards and calendar listings on other pages show the same
- Event map pins are placed at a slightly offset position (not the exact address)
- Public calendar feeds (ICS) show the city and state only
Where the full address is still shown:
- The RSVP confirmation page (shown immediately after someone RSVPs)
- RSVP confirmation emails and calendar invites
- Host Tools pages
- The dashboard (for Team Members)
This setting is independent of the "Hide Location Address in Calendar Invite" option in event automations. That setting controls whether the street address appears in the calendar attachment sent with confirmation emails. The two can be used together or separately depending on your needs.
This option only appears for in-person events. Virtual events don't have a physical address to hide.
Pre-selecting Event Sessions via URL
For multi-session events (such as a weekend intensive with Saturday and Sunday sessions), you can pre-select specific sessions by appending the event_session_ids parameter to your event page URL.
Example:
https://yoursite.solidarity.tech/leadership-intensive?event_session_ids=12345,12346
When someone opens this link, the specified sessions will already be checked on the form. This is useful when:
- An event spans multiple days and you want all sessions selected by default
- You're sharing a link for a specific combination of sessions
- You want to encourage sign-ups for all listed dates without requiring manual selection
How to find your event session IDs:
- In the dashboard, go to Events and open your event
- Click the Schedule tab
- Click Edit on any session. The session ID is the number at the end of the URL (e.g.
/events/100/calendars/12345/editmeans the session ID is12345) - Alternatively, use the API:
GET /api/v1/event_sessions?event_id=EVENT_IDreturns all sessions with their IDs
To pre-select multiple sessions, separate the IDs with commas: ?event_session_ids=12345,12346
Pre-selected sessions can still be unchecked by the user before submitting. This feature pre-fills the selections but does not enforce them. To require all sessions, set "Event Session Selection" to "Only One" and create a single combined session, or include instructions in your event description.
Selling Tickets (Ticketed Events)
Event pages can sell tickets instead of collecting free RSVPs. Buyers choose a ticket type and quantity, pay by card, and get an RSVP with their order attached.
To sell tickets you need a Stripe account connected with payouts enabled. Ticket revenue is paid out directly to your connected Stripe account.
Enable Ticketing
- Open the event page in the dashboard and go to Basics
- Scroll to Event Page Settings
- Toggle Sell tickets
- Choose the Stripe account for payout (only accounts with payouts enabled appear)
- Select the currency for ticket sales (USD, CAD, GBP, EUR, or AUD)
- Add at least one ticket type
- Save
Turning on ticketing changes how this event works: attendees register for one session per order (the "Any Number" session selection option is disabled), the session waitlist is turned off, and the RSVP confirmation email is turned on and locked, because it carries the buyer's order summary. Saving requires a payout account and at least one ticket type.
The currency cannot be changed after the page is created.
Ticket Types
Click Add Ticket Type to create each type of ticket you want to sell. Each ticket type has:
| Field | Details |
|---|---|
| Name | Shown on the event page (e.g. "General Admission"). Up to 80 characters. |
| Price | Per ticket. Enter 0 to make the ticket free; paid tickets must be at least 1.00. |
| Description | Optional text shown below the ticket name. Up to 300 characters. |
| Available per session | Optional cap on how many tickets of this type can be sold per session. Leave blank for unlimited. |
You can add up to 20 ticket types. Maximum tickets per order (default 10, up to 100) limits how many tickets one person can buy in a single order, across all ticket types.
What Buyers See
The event page shows a Tickets section listing each ticket type with its price and a quantity selector. The payment card field only appears when the order total is above zero; an order made up entirely of free tickets skips payment.
- Buyers select one session per order
- Ticket types that hit their per-session limit are labeled Sold Out
- A session that reaches its Max Capacity is labeled sold out and can't be selected
Capacity and Seat Counting
Session Max Capacity counts seats, not RSVP rows: a buyer who purchases 4 tickets takes 4 seats even though they appear as a single RSVP. Per-type "Available per session" limits are enforced on top of overall session capacity.
Team Members can still add attendees from the dashboard without an order (for example, comped guests). Those RSVPs take one seat each.
Where Sales Show Up
- Schedule tab: each session shows tickets sold per type (e.g. "General Admission: 12/50 sold")
- RSVP list and Host Tools: buyers appear with a party size badge and a breakdown of what they hold (e.g. "2 × General Admission, 1 × VIP")
- Finances → Payments: each order appears in the payments ledger, with an itemized ticket breakdown on the payment detail page
- Confirmation email: the buyer's RSVP confirmation includes their order summary and receipt reference
Refunds
Refund a ticket order from its payment detail page under Finances → Payments. Full refunds issued directly in Stripe sync back automatically. When a buyer's orders are fully refunded, their seats are released and their RSVP is moved to "No". A refunded buyer can't restore their RSVP to "Yes" without purchasing again.
For more detail on how ticketing affects RSVP behavior, see RSVPs.
Updated 29 days ago
