Organization vs. event pages
Pages live at one of two levels, and choosing the right one keeps your content organized.
Organization pages
Organization pages belong to your whole organization, not a single event. Use them for content that outlives any one event — an about page, a contact page, or a homepage that lists your events. They share your organization's layouts and branding.
Because these pages span every event, they offer an Events list block that isn't available on event pages. Drop it onto an organization page to show an automatic grid of your events — each card pulls the event's name, location, start date, and banner (falling back to the logo when no banner is set) and links straight to that event's page. New events appear on their own, so a homepage built this way stays up to date without editing.
Event pages
Event pages belong to one specific event. Use them for everything tied to that occasion — the landing page, schedule, venue details. Event pages also support requiring sign-in, so you can keep certain pages visible only to logged-in users.
Which should I use?
- Content about your organization or spanning many events → organization page.
- Content about one specific event → event page.
Public addresses
Both kinds are served under your address (and any custom domain you connect). A custom domain can point at either an organization or a single event, so you can give an important event its own clean web address.
Reusable headers and footers are also scoped this way — see Layouts.
Was this helpful?