Ban a Ride

An operator bans a ride that violates platform policies, making it immediately unavailable to all users.

Wishlist — not yet planned. Ride banning will be revisited after launch if a need is established. The design below captures intent but has not been finalized or committed to a release.

Who Can Do This

  • Operator — via the back office at https://admin.95octane.app.

Steps

  1. Locate the ride in the back office.
  2. Select Ban Ride.
  3. Enter a reason for the ban.
  4. Confirm the action.

What Happens Immediately

  • Participants with yes or maybe RSVP status lose access to the ride, navigation, and intercom.
  • The ride is hidden from Discovery (public rides).
  • The ride link is invalidated — users with the link who have not yet RSVPed cannot open the ride.
  • The ride creator and all participants with yes or maybe RSVP status receive a push notification.
  • The ride remains visible in each participant's Ride History as unavailable.

Lifting a Ban

An operator can lift a ride ban at any time via the back office. When lifted:

  • The ride returns to its pre-ban state and status.
  • Access is restored for all participants.
  • The ride reappears in Discovery (public rides) and via its link (private rides).
  • No notification is sent to the creator or participants when the ban is lifted.

Rules

  • Ride banning is extremely rare and reserved for clear policy violations.
  • The ban takes effect immediately — there is no token-expiry delay.
  • A banned ride is not deleted. Its data is preserved in Firestore.
  • The ban reason is visible to the operator in the back office but is not shown to participants.
  • Only the creator is notified. Participants with yes/maybe status receive no notification — the ride simply becomes unavailable to them.