GatherPress

Last updated July 11, 2026, Version 0.34

• Documentation for users

• Core concepts
• Getting started
• Creating and managing events
• Topics
• RSVP system
• Blocks
  • Event Query block
  • RSVP and Inner Blocks
  • RSVP Response and Inner Blocks
• Venues
• Emails
• Calendar feeds
• Displaying event-related information elsewhere (ID Override)
• User roles and permissions
• Update your privacy policy
• Where to get help

This section explains how RSVPs work from both the visitor and organizer perspectives.

RSVP Mode

Site administrators can control how RSVP works across the entire site from Events → Settings → RSVP. Four modes are available:

• All Events — RSVP is enabled for every event. No per-event toggle is shown in the editor. This is the default behavior.
• Per Event (default on) — An Enable RSVP checkbox appears in the RSVP settings panel of the editor for each event. New events default to RSVP enabled; editors can disable it per event.
• Per Event (default off) — Same as above, but new events default to RSVP disabled. Editors must explicitly enable RSVP for each event.
• Disabled — RSVP is turned off sitewide. RSVP blocks are removed from the block inserter, the RSVPs admin menu is hidden, and the RSVP Settings panel no longer appears in the editor.

RSVP functionality

RSVPs are configured per event.

What is known and visible in the UI:

• The presence of the RSVP block allows users to RSVP
• Default RSVP behavior comes from GatherPress settings.
• Event-level settings override global defaults.

Open RSVP (without an account)

Open RSVP is enabled by default. Site administrators can disable it sitewide from Events → Settings → RSVP by unchecking Enable Open RSVP for Events.

While it is enabled sitewide, it can also be switched off for an individual event with the Enable Open RSVP checkbox in the RSVP settings panel of the editor. Open RSVP itself shipped in 0.33.0 — what 0.34.0 adds is this sitewide on/off control and the per-event override.

When enabled, visitors can RSVP using only their name and email address. An email with a confirmation link is sent to the visitor, and the RSVP is only confirmed after the link is clicked or an administrator approves it manually.

When disabled:

• The RSVP Form block is removed from the block inserter.
• Any RSVP Form blocks already placed on an event render nothing on the frontend.
• Direct form POST or REST API submissions return a 403 response.

Managing RSVPs

Event organizers can manage RSVPs from the WordPress admin.

What is visible:

• A list of RSVPs per event.
• Attendee status (yes / no / waiting list, if applicable).
• Ability to approve, unapprove, delete or mark as spam manually when hovering, same as comments.
• if a red dot appears in the RSVP column, it means the RSVP is pending.

Capacity and limits

Events can define attendance limits.

What is confirmed:

• Total number of people allowed at the event. A value of 0 indicates no limit.
• A maximum number of guests per attendee can be set.
• Defaults come from global settings.

What happens when an event is full:

• New RSVPs are prevented once the limit is reached.
• A waiting list may be used if enabled. If enabled and someone is on a waiting list and a spot opens up, they are moved to attending. For now, no email is sent.

Anonymous RSVP

If checked, visitors will be able to select “List me as anonymous”. Their name and avatar will then not be publicly displayed, but admin users will still know their name and email addresses.