Floor Plans & Layouts
Venue Owner Guide
4 min read
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
The Designer is where you break a venue down into zones — standing areas, seated sections, stage, VIP and so on — and, inside a seated zone, an actual grid of seats. It is what organisers see as your venue’s real layout, distinct from the seat map an organiser later builds for their own event.
How to build a layout
- Open a venue and click Open Designer (or My Venues → venue → Designer).
- Add a zone — give it a name, a type (Standing Area, Seated Section, Stage, Backstage, VIP Area, General Admission), a colour and, optionally, a capacity cap.
- Generate a grid — inside a zone, set rows and seats-per-row and click Generate. Rows are lettered A, B, C… and seats numbered 1, 2, 3… automatically. If the zone has a capacity set, a grid that would exceed it is rejected with an error instead of silently overshooting.
- Drag seats to fine-tune — on the canvas, drag any seat to reposition it; the position saves automatically as you drop it.
- Reorder or edit zones — rename, recolour or change a zone’s type and capacity at any time from its panel in the sidebar.
Settings explained
- Zone type — purely descriptive (drives the colour tag and icon shown to organisers); it does not restrict what seats you can add inside it.
- Zone capacity — an optional hard ceiling. If set, Generate Grid refuses to create more seats than the capacity allows; it does not automatically shrink a grid you request that is too big, it just blocks the action.
- Generate Grid — regenerating a zone that already has seats deletes and replaces every seat in that zone, including any manual position tweaks you made. You are asked to confirm before this happens.
- Delete zone — removes the zone and all of its seats; also asks for confirmation first.
Good to know — who actually builds the seating chart
- This designer describes your venue, as a reusable template. It is what shows up as the “Zones” summary and seat counts on your venue’s public and detail pages, and it is what an organiser sees before requesting your space.
- It is not the same thing as the seat map an organiser uses to sell reserved-seating tickets for their event — that is a separate structure the organiser builds inside their own event.
- The one bridge between the two: if an organiser owns an event and directly assigns one of their own venues to it, they get a Clone Layout action on the event’s venue page that copies your zones and seats into that event’s seat map (zone → section, seat → seat, one-for-one). Cloning replaces any seat map the event already had.
- Crucially, this only applies when the organiser owns the venue directly. When an organiser instead rents your venue through a booking request — the normal marketplace path — there is no cloning available to them: they build their event’s seat map from scratch, independent of anything you set up here. Your zones and seats stay purely informational for that organiser — a preview of what the space can hold, not something they inherit automatically.
- After a clone, the copied sections have no ticket type attached yet — that assignment is a separate step the organiser does afterwards, outside this designer.
Troubleshooting
- Generate Grid did nothing / showed an error — the requested rows × seats-per-row exceeds the zone’s capacity; raise the capacity or ask for a smaller grid.
- My careful seat positions disappeared — someone ran Generate Grid again on that zone; it always rebuilds the zone’s seats from scratch rather than adding to them.
- An organiser I rented to says they cannot see my seat layout on their event — that is expected: cloning a venue’s layout into an event only works for an organiser assigning their own venue, not for a rented booking. They need to build the event’s seat map themselves.
- I do not see an option to upload a floor-plan image or PDF — there is not one; the designer is a live zone/seat builder, not an image-upload feature.