Event-wide settings for session registration (RSVP): whether attendees can reserve seats in sessions that run at the same time, and what they see when a session needs registration, is booked or is closed.
Before you start
You need to be an organization admin or an event admin.
These settings apply to sessions with Enable registration (RSVP required) on. See Define session capacity and track RSVPs.
Each switch saves as soon as you change it ("Saved").
Where to find it
Content > Schedule > Settings in the admin panel, section RSVP.
Change the status messages
Under RSVP status text, select Edit.
Change Registration Required, Registration Confirmed and Registration Closed. Each text is required ("This field is required") and up to 50 characters ("Maximum length is 50 characters").
Select Save.
Registration Closed can be edited only while Show RSVP disabled text in app is on. The current texts are previewed under the setting; the closed text only while that switch is on.
Settings
Setting | What it does | Default |
Allow overlapping RSVPs | Attendees can reserve a seat in a session that overlaps a session they already reserved. When off, they must cancel the overlapping reservation first. | On |
RSVP status text > Registration Required | Message on sessions that need registration, including sessions that need your approval. | "This session requires registration." |
RSVP status text > Registration Confirmed | Message after the attendee has reserved a seat. | "You've registered for this session." |
RSVP status text > Registration Closed | Message when the session is full or Allow registrations via app is off for the session. Also shown on a full session with a waitlist and to attendees on the waitlist. | "This session no longer accepts registrations." |
Show RSVP disabled text in app | Shows the closed message on the session page and the "RSVP required" label on schedule cards for full or closed sessions. When off, both are hidden for those sessions. Full sessions with a waitlist still show the closed message. | On |
Show RSVP button disabled state | Shows a disabled Reserve seat (or Request seat) button on full or closed sessions. When off, the button and the seat count are hidden for those sessions. The bookmark button stays. | On |
How overlapping RSVPs work
An attendee selects Reserve seat or Request seat for a session that overlaps one where they already have a seat. The app opens the Overlapping sessions sheet with the conflicting sessions.
With Allow overlapping RSVPs on, the sheet says "You are attending another session at the same time, would you like to RSVP anyway?" and offers RSVP anyway and Back to session.
With Allow overlapping RSVPs off, the sheet says "In order to RSVP for the new session, you need to cancel any overlapping sessions first." and offers only Back to session.
Only seats count as overlaps: confirmed and attended registrations. Requests waiting for approval and waitlist places don't.
Brella checks overlaps on its side too, while Allow overlapping RSVPs is off:
It refuses a seat the attendee reserves with "You already have a confirmed place in an overlapping session."
It rejects a waitlist place or a pending request of an attendee with an overlapping seat. This happens when Brella would confirm it: when a seat opens up, or when you turn off approval or the waitlist.
Registrations you add or approve in the admin panel, and registrations added through the API, are not checked.
An attendee can always join the waitlist of a full session, even with an overlapping seat. The sheet then offers Join waitlist and Cancel. With Allow overlapping RSVPs off, it says the attendee will get a seat only if they cancel the overlapping session first. If Brella rejects the waitlist place, the app shows "Not confirmed due to an overlapping RSVP", and the attendee can register again.
Meetings are checked separately. Networking > Settings > RSVP - meeting conflict handling > Prevent overlaps between RSVPs and meetings (off by default) stops attendees from booking a meeting during a session where they have a seat, and from reserving a seat, requesting one or joining a waitlist in a session that overlaps a meeting. It also applies to registrations you add or approve in the admin panel, and to seats given from a waitlist. See Networking settings.
What attendees see
On the session page: the status message for the session's state and "N seats left" when a capacity is set and registration is open. The button reads Reserve seat, Request seat, Join waitlist, Cancel RSVP, Cancel request or Leave waitlist.
On schedule cards: "RSVP required" for sessions where the attendee has no seat yet.
Fixed messages you can't change: "Your registration is pending approval", "Your RSVP was not confirmed" and "Not confirmed due to an overlapping RSVP".
The Overlapping sessions sheet when they register for a session that overlaps one where they already have a seat.
The mobile app and the web app show the same screens.
Limits
Each status text is 1 to 50 characters.
Per-session options (capacity, approval, waitlist, cancellations, QR code tickets, who can see the attendee list) are in each session's Preferences tab, not here.
Troubleshooting
Attendees say they can't reserve a seat
The session is full, Allow registrations via app is off for the session, or the attendee has an overlapping seat while Allow overlapping RSVPs is off. Check the session's Preferences and this section.
"Not confirmed due to an overlapping RSVP"
The attendee was on the waitlist and had a seat in an overlapping session when a seat opened up, while Allow overlapping RSVPs is off. They can cancel the other seat and register again.
Nothing shows on a full session
Show RSVP disabled text in app and Show RSVP button disabled state are both off. Turn on at least one.
The Registration Closed text is greyed out
Show RSVP disabled text in app is off. Turn it on to edit the text.