Bookitive
Events

Event settings

A map of every event settings tab — general, payment methods, sales booster, anti-scalping, dynamic pricing, emails, team, and the danger zone.

Not verified yet

Event settings (the footer item of the event sidebar) gathers every switch that changes how one event behaves. This page is the map; each deep topic links to its own guide.

General

The identity fields — name, slug, start/end (plus an optional doors-open time that feeds check-in and the arrivals curve), timezone, place or online URL, currency, venue — plus the behavior settings that matter more than they look:

  • Language — Czech or English, setting the language of this event's PDF ticket labels and invitations. (Buyer transactional emails stay Czech-only, independent of this.)
  • Ticket delivery — how buyers receive tickets: a PDF attached to the email, a link to a hosted ticket page (with open and download tracking), or rotating QR codes (online or offline mode) that make screenshots useless to scalpers. Details: Delivery modes.
  • Ticket transfers — whether a ticket can move to another device freely, only after email verification, or not at all: Transfers.
  • Waitlist — collect signups once a type sells out, with an offer validity window and a max tickets per signup cap (the party size one person can claim — default 4, range 1–50). The waitlist controls themselves sit in the Payment methods card below: Waitlist.
  • Show "reserved" publicly — whether buyers see seats held by unpaid reservations as distinct from sold. Showing them communicates scarcity honestly; hiding them keeps the map simpler.
  • Pause all sales — the red switch. Public sales stop instantly, the box office keeps working, and your check-in is unaffected. Flip it back anytime. Right under it, set an optional paused-sales message (up to 280 characters) shown to buyers on the public page while the pause is on.

Payment methods

Which of the five methods this event accepts — bank transfer, card (terminal), cash, pay at the door, complimentary. At least one must stay enabled. New events start with bank transfer, card, cash, and complimentary; pay at the door is opt-in. See Payments for how each behaves.

Sales booster

The urgency signals on the public page — the low-stock line and the recent-orders social proof, with a live preview. See Sales booster.

Anti-scalping

Per-event protections: require attendee names on tickets, require a verified phone at checkout (with accepted prefixes), and the risk-action ladder for suspicious orders — seeded from your organization defaults. See Protection.

Dynamic pricing

An event-wide view of every ticket type's scheduled price phases on one screen, with overlap warnings and validation. See Price phases.

Emails

A pointer to the event's email overrides — per-event copy and enable/disable switches layered over your organization texts.

Team

Per-event staff: grant Event manager, Box office, Scanner, or custom event roles to people by email — including people who aren't Bookitive users yet (they get an invitation). Organization members who already have access through org-wide roles are listed for clarity. See Event staff.

Danger zone

Three irreversible-feeling actions, in increasing severity:

  • Cancel event — type-to-confirm; sales stop for good and the event is marked cancelled. Orders and reports remain for your records.
  • Unpublish — back to draft; the public page goes dark, data stays. Only shown while the event is on sale.
  • Delete event — type-to-confirm; permanently removes the event and everything in it. Only for events that never really happened.

Cancelling or deleting does not automatically message buyers or refund orders. Handle communication and refunds first, then close the event down.

On this page