How OpenRSVP Works

Magic links, zero accounts, privacy-kept events.

OpenRSVP is designed for communities that want effortless invites without giving up control of their data. Themes and saved keys stay on your device only.

Capability tokens only Hosts can’t edit guest RSVPs Optional RSVP approvals Automatic decay cycles Catppuccin themes

Quick start

  1. Create an event, pick a channel (optional), and set privacy.
  2. Share the public link. Guests get a one-time RSVP token after submitting.
  3. Keep the admin link private; hosts cannot impersonate guests.
  4. Use Preferences to pick a theme or forget saved magic links.

Creating events

  • Channels are optional. Use them to group events for a community.
  • Suggestions appear as you type; picking one reuses that channel.
  • Start/end times respect viewer timezones; durations render automatically.
  • Private events stay hidden even if the channel is public.
  • Descriptions support basic Markdown for richer details.
  • Toggle “Require admin approval for new RSVPs” if you want to approve guests before they show up.
  • Use “Close RSVPs” to pause new submissions or set an auto-close time that flips the toggle for you.

Channels & visibility

  • Public channels show up on the homepage and at /channel/<slug>.
  • Private channels are hidden; only people with the slug can view /channel/p/<slug>.
  • Public events inside private channels hide the channel badge to protect the slug.
  • Channel privacy never overrides an event’s own privacy.

Channel Naming tips

  • Names automatically become web-safe links: we lowercase them and swap spaces or punctuation for hyphens.
  • Avoid generic names to prevent collisions—add city or group hints.
  • Private channel slugs are the secret; share them carefully.

RSVP privacy controls

  • Guests can hide their RSVP from the public list; organizers still see it.
  • Each submission returns a magic link to edit, toggle privacy, or delete.
  • Public counters show total visible guests; private RSVP counts are summarized.
  • When approval is required, new RSVPs start as pending until the host approves or rejects them.

Magic links & storage

  • Magic links are shown once and can be copied with inline buttons.
  • Your browser can remember admin/RSVP keys locally to surface “Open Admin” or “Edit your RSVP.”
  • Clear saved keys anytime from Preferences or via “Forget this key” on event/RSVP pages.

Themes & polish

  • Pick between Catppuccin Latte, Mocha, Frappé, or Macchiato in the Preferences menu.
  • The selection persists per-device; respects system dark mode until you override.
  • Copy actions surface toast confirmations so you know the link was saved.

Event capacity limits

  • Some events include a maximum number of attendees.
  • When that cap is reached, the Yes option is temporarily unavailable and you'll see a “full” note.
  • You can still RSVP as Maybe or No; those do not reserve a seat.
  • If space opens, the Yes choice reappears automatically and you can change your RSVP back.
  • Maybe is just a signal—it does not hold a spot for you.
  • A simple waitlist may be offered in the future; for now the flow stays predictable.
  • Hosts can close RSVPs entirely (manually or on a schedule); existing guests can still edit or delete their entry.

Closing RSVPs

  • The event owner view includes a “Close RSVPs” toggle—flip it any time to pause new submissions instantly.
  • Set an optional auto-close time while editing an event and the system will flip the toggle for you once that timestamp passes.
  • Times honor the timezone you entered for the event; behind the scenes they are stored in UTC so the close happens as soon as the backend sees that moment has passed.
  • When closed, new guests see a clear message instead of the RSVP form, but anyone with an existing magic link can still edit or delete their entry.
  • Reopen RSVPs by turning the toggle back off—scheduled close times clear automatically after they run so you can pick a new one.

Add to Calendar (.ics)

Every event now includes an “Add to Calendar” button to download a universal .ics file.

  • Works on iPhone / iPad (Apple Calendar)
  • Android Calendar
  • Google Calendar (import)
  • macOS Calendar
  • Windows Outlook

How it works: tap or click the file and your device offers to add the event directly to your calendar.

Safety & privacy

  • No accounts, emails, or analytics are stored. Magic links stay local to your device unless you share them.
  • Hosts cannot change guest RSVPs—only guests can edit their own details.
  • Private RSVPs hide from other guests; hosts still see full details.
  • Events, RSVPs, and channels decay automatically unless they stay active.

Lifecycle & control

  • Event owners can update event details, assign channels, delete RSVPs on request, or delete the entire event (removes all RSVPs).
  • Hourly decay hides stale events; purged items cannot be restored. Root admin can trigger decay via CLI.
  • Channel privacy is independent from events—set them separately to match your invite style.

Need more? Reach out to your event owner directly—OpenRSVP never stores contact info.

Have feedback or spot a bug? Open an issue on GitHub.