Web app

Using OpenRSVP in the browser

Event creation, RSVPs, and channels with a Catppuccin Latte coat of paint.

UI Latte theme

Create an event

Pick a title, optional description, start/end time, location, and channel. The app slugifies the channel name and reuses it when the slug + visibility match.

Visibility: private events stay hidden from public listings; public events show up on the homepage and their channel if the channel is public.

Event owner link: shown once after creation at /e/<event-id>/admin/<admin-token> and acts as the owner/admin console. Save it—there are no accounts to recover it later.

Approval gate: toggle “Require admin approval” to keep new RSVPs pending until the event owner approves or rejects them in the owner view.

RSVP window: flip “Close RSVPs” at any time or schedule an auto-close timestamp that toggles the switch for you.

The event owner page lets hosts edit details or delete the event entirely (which also removes all RSVPs).

RSVP flow

Guests submit name, pronouns, status (yes/maybe/no), guest count, and notes. They immediately see their RSVP magic link and can store it locally for quick edits.

  • Public vs. private RSVPs (hide from attendee list; organizers still see them).
  • Edit or delete your own RSVP anytime using the token link.
  • Events with approval enabled hold new RSVPs as pending until the host marks them approved or rejected.
  • When approval is required, the event location stays hidden until a Yes RSVP is approved.
  • Guests can message the organizer from their RSVP link; replies appear in the RSVP message feed.
  • Organizers can delete RSVPs on request but cannot change their contents.
  • Hosts may close RSVPs entirely (manually or scheduled); existing guests retain edit/delete access via their token.

Channels & browsing

Channels keep related events together without accounts.

  • Public channels appear on the homepage filter and /channel/<slug>.
  • Private channels never list publicly; they are reachable only by URL.
  • Channel badge hides on public events inside private channels to avoid leaking the slug.
  • Use /channels/discover to search, sort by rank/name/recent, and filter to channels with upcoming events.

Magic links, privacy, and preferences

The UI stores event owner (admin) / RSVP tokens locally (when the browser allows) so visitors can reopen “Edit” actions. Use Preferences or per-event “Forget this key” to clear saved links.

The /my-events and /my-rsvps pages list saved links for this device only.

Catppuccin themes are available in the app; this docs site sticks to Latte for consistency.

Never share event owner/admin or RSVP tokens publicly. They are the only credentials OpenRSVP uses.

Decay and cleanup overview

APScheduler runs hourly to decay scores for events, RSVPs, and channels. Low-score or expired items disappear from listings and are purged when empty.

  • Upcoming events are never purged; deletion waits for the event to finish plus a grace window.
  • Root admins can trigger openrsvp decay manually.
  • Deleted events and purged data are not recoverable.

See the dedicated decay & cleanup page for deeper tuning guidance.

Sharing and invites

Every event page includes sharing helpers for guests.

  • Copy the RSVP form link directly.
  • Use the Share button for native sharing on HTTPS (falls back to copy).
  • Scan the QR code to open the RSVP form on another device.

Announcements and messaging

Event owners can post public announcements and direct messages.

  • Announcements appear on the public event page.
  • Owners can send private messages to a specific RSVP.
  • Admin-only notes stay visible just to organizers.
  • Guests can reply from their RSVP edit page.

OpenRSVP · FastAPI · SQLite · Catppuccin Latte