Create an in house event

PASSING GATE Venue Manager 8 steps · 33.5s · recorded Aug 30, 2:42 PM · 3499cea

This run has no video.

Speed 0.5× 1× 1.5× 2×

Source: e2e/scenarios/test_wf_file_an_in_house_event.py:1 · run 20260830T214128Z-3499cea · steps carry start_ms/end_ms offsets into the video

Steps

The same intake pipeline as the public Host-an-Event form, behind an `employee` gate. Not a second pipeline — a second front door onto the one that already exists.
Event, description, date, headliner, flyer. Everything else — the whole run of show, the head counts, all three tiers — is already answered below.
Booked means a PUBLISHED event — an approved application does not hold the date. The server asks the same question again on submit.
Collapsed on a phone, open where there is room, and never hidden: a person filing an event is agreeing to a 5:30pm load-in and a $68 door, and every one of these is editable.
390x844 — the size the owner reviews on. The defaults panel is collapsed here, so the five answers and the file button are what is on screen.
Required here, recommended on the public form. Staff have the artwork in hand, and it is the input to the social campaign.
One press. Everything else on this screen was typing, and the whole run of show, three tiers and the head counts were already answered.

Adding a note needs JavaScript — it pauses the video and captures the current frame. The notes themselves are always readable at /my/annotations.

Run history (5)