Overview

A venue describes where an event takes place. A seat map describes the layout customers use when choosing reserved seats there. Keeping those two concepts separate helps you reuse a venue while offering different seating arrangements.

Choose the seating approach

For general admission, customers choose ticket quantities and price tiers; they do not select named seats during booking. For reserved seating, the map identifies the sections, rows, and seats customers can choose.

Start with the venue's details, then prepare a seat map if you need reserved seating. Check the real room's layout and numbering before publishing a map for customers to use.

Seat maps

A map combines sections and rows with seat positions and labels. The stage and section names help customers orient themselves. Seat categories let you group seats for pricing, while properties such as accessibility or obstructed view communicate characteristics customers may need to consider.

For example, a community hall might have one Main Floor section with six rows, but a larger venue could need several separately numbered sections. Use a layout that reflects the actual venue rather than relying on a generic arrangement.

Understand map versions

Saving changes creates a new map version. Older versions are read-only; Open Latest returns you to the editable version. Check the version and layout before using a saved map in an event.

Create and version a seat map explains the workflow. Rows, sections, categories, and seat properties have separate editing guides in this section.

Separate layout from availability

A physical seat existing on a map does not mean it should be available for every event time. After configuring the event, use event-time seat availability to block seats or make selected seats accessible through a code. This is a different decision from changing the venue's layout.