Setting up your event

This walkthrough takes a new event from nothing to “ready to open”. Each page is an outline: a short list of what must exist first, the steps in the order that works, and a ready check at the end.

Do the first page first. After that the modules are independent — set up only the ones your event uses, in any order.

#	Page	You will have
1	Create the event	A Stripe key, an event with its modules switched on, event admins, and working permissions.
2	Register	Tiers, merchandise, e-mails, a primary registration form that is open, badge numbering, and a badge label.
3	Vendors	Table sizes, payment settings, e-mails, a vendor type with an application form, and a vendor checklist for every vendor type.
4	Schedule	Rooms, tracks, e-mails, and a category with a submission form that panelists can fill in.
5	Staff	Departments, open positions, staff settings, and onboarding flows.
6	Shop	Items on a public storefront, plus the fulfillment and point-of-sale stations to hand them over.
7	Inventory	A tag prefix, registered assets and boxes, and logistics terminals.

Two places you will work

	Management portal	Event site
Address	Your organization’s address, for example https://yourorg.midsummer.cloud	The event’s own address, for example https://yourevent.midsummer.cloud
Who can sign in	Organization admins only	Everyone — what you see depends on your permissions
What you do there	Create events, add Stripe keys, manage domains, name event admins	Everything else: every module’s settings, forms, and tools

The management portal has no “open this event” button. To get to an event, type its address into your browser.

Three kinds of admin

Setup stalls most often because the right person does not have the right role. There are three, and holding one does not give you the others:

Organization admin

Can sign in to the management portal. Creates events and Stripe keys.

Event admin

Named per event. Can open Event Management on the event site (modules, time zone, event active). An event admin is also treated as leadership of every department attached to the event.

Module admin

Comes from a department that owns the module. This is what unlocks a module’s admin menus — Registration Settings, Marketplace Settings, and so on. See HR & permissions.

Important

Being an event admin is not enough to configure a module. If a module’s menu shows only its public pages, no department attached to the event owns that module yet. Fix it in Step 5 — Make sure someone can administer each module.