Approve or Reject an RSVP

The ride creator or an admin reviews and acts on pending RSVP requests for rides that require approval.

Who Can Do This

  • Creator
  • Admins

Only applies to rides where Require RSVP Approval is enabled.

Steps

  1. Open the ride's participant list.
  2. Review the list of pending RSVP requests.
  3. For each request, choose to approve or reject.

Rules

  • Pending RSVPs only exist on rides with Require RSVP Approval turned on. Rides without this setting have no approval queue.
  • Pending requests do not expire. The creator and admins can approve or reject them at any point while the ride is upcoming or on-going. Once the ride's end time passes, the approval queue is closed and remaining pending requests are deleted as part of archival.
  • Approving a request converts the participant's status from pending to yes and grants them access to navigation and intercom. Because pending RSVPs already consume a maxRiders slot, approval does not consume an additional slot — it only reclassifies the existing one. Approval is never blocked by capacity.
  • Rejecting a request removes the pending entry, adds the user to the ride's block list, and notifies them. A rejected user cannot re-RSVP to this ride.
  • If a user with a pending RSVP changes their own status to no before the request is reviewed, the pending entry is removed and their maxRiders slot is freed immediately. The creator and admins no longer see the request in the approval queue.
  • The creator and all admins can approve or reject — approval is not limited to one role.
  • If the creator turns off Require RSVP Approval while requests are pending, they are shown a confirmation prompt explaining that all pending requests will be auto-approved. If confirmed, the setting is disabled and a background process auto-approves all pending requests in first-in, first-out order (oldest submission first), subject to the same validations as manual approval. Requests that fail because the ride is full are rejected, the user is added to the block list, and they receive a "Ride is full" notification (not a generic rejection). If the creator cancels the prompt, the setting remains unchanged.

What Happens Next

  • Approved: the participant joins the ride with yes status, gains access to navigation and intercom features, and receives a notification that their RSVP was approved.
  • Rejected: the participant is removed from the pending list, added to the ride's block list, and notified. They cannot re-RSVP to this ride unless the creator unblocks them. The ride appears as unavailable if they follow a direct link, and is hidden in Discovery. See Remove a Participant for block list behavior and the unblock flow.

Failure Cases

  • Ride does not require approval: there is no pending queue on rides where RSVP approval is not required.
  • Not authorized: only the creator or an admin can approve or reject RSVPs.

Status: partially-live. Backend API (approve and reject endpoints) is complete. Frontend UI for the approval queue is not yet built.