DG EventsHelp center
πŸ“– All help topics

πŸ› οΈ Organizer console & creating an event

Get into /admin, create or clone an event, and find your way around the per-event hub.

πŸ” Getting into the console

The organizer console is at /admin, and there are two kinds of access.

TierWhat it gets you
Event organizerThe full console for the events you organize, and nothing else. This is the tier a conference team lives in. An existing organizer adds you by email from the event's πŸ‘₯ Organizing team panel; you don't need an account first, you just sign in with a magic link.
Platform adminEvery event, plus the ability to create and clone them. Set at the deployment level (APP_ADMIN_EMAILS), so adding one is a job for whoever runs the deployment.

Practically: the first person is a platform admin, they create the event, and then they add the rest of the team as organizers from inside it.

ℹ️ Note
Whoever creates an event is recorded as its first organizer. Organizer role also gets the privileged view of the event's public pages β€” ticket-gated video without a ticket, and the block controls in the People directory.

πŸ‘₯ Adding your team

Open πŸ‘₯ Organizing team on the event hub, type a colleague's email and press Add organizer. That's the whole process β€” they sign in with a magic link and land in the console with your event waiting.

⚠️ Heads up
An organizer gets everything for that event: refunds, attendee data exports, the budget, campaign sending. There are no finer-grained roles, so add people you'd trust with all of it. You can remove someone any time, though the console won't let you remove the last organizer.

πŸ—‚οΈ The console home

/admin lists every event, newest first, each with its URL slug, start date and a status pill β€” published in green or draft in grey. Click an event name for its hub. Top right is + New event.

✨ Creating an event

+ New event starts with a description rather than a blank form. Describe the conference in plain English and the assistant drafts the whole thing β€” name, slug, dates, timezone, venue, description and ticket types with early-bird pricing. Nothing is created until you've reviewed it.

  1. Describe it. The form's own example is worth copying in shape: "Three-day genetic genealogy conference in Boston next August, hybrid. In-person $249 with $199 early bird through May, virtual $99, comp tickets for speakers." The more specifics β€” dates, prices, formats β€” the less you edit.
  2. Press ✨ Draft it.
  3. Review the draft. Every field is editable: name, URL slug, description, start, end, timezone, and each ticket type with its price. Fix anything the assistant guessed wrong β€” particularly the slug and the timezone, which are awkward to change later.
  4. Press Create event (as draft). It's created unpublished, so nothing is public yet.
πŸ’‘ Tip
An early-bird price becomes a scheduled price change: the ticket starts at the early-bird figure and a "Regular" schedule takes over on the date the early bird ends. No manual switch on the day.

⧉ Cloning last year's event

For a recurring conference, ⧉ Clone event on an existing event's hub is much faster than starting over.

ClonedNot cloned
The event itself (as a draft), ticket types, price schedules, add-ons, registration form fields, promo codes, rooms, tracks and sessions β€” with room and track links remapped to the new copy.Orders, tickets, participants, speaker assignments and check-ins. Last year's attendees are not carried over.

Clone, then fix the dates β€” the sessions come across on their original dates, so the agenda needs shifting to the new year.

🚦 Publishing

The button beside the event name on its hub toggles between Publish and Unpublish. Draft events are invisible: they don't appear in the public directory and their pages return "not found". Publishing makes everything live at once.

⚠️ Heads up
Unpublishing an event that's already selling takes the pages away from people who have tickets, so use it to pull an unannounced event rather than to pause a live one.

🧭 The event hub

Clicking an event opens its hub β€” the top of the page is a row of links to every other console section, and the rest of the page is the things you do most often.

SectionWhat it covers
πŸ“· Check-in scanner Β· πŸ–₯ Kiosk modeπŸ›‚ Onsite: check-in, kiosk & badges
πŸ“₯ Import agenda Β· πŸ—“ SessionsπŸ“… Building the agenda
🎀 Speakers🎀 Speakers console, fees & expenses
βœ‰οΈ Commsβœ‰οΈ Email, SMS & push
πŸ“ SurveysπŸ’¬ Surveys, chat rooms & moderation
πŸ“£ SocialπŸ“£ Social publishing
πŸͺ Exhibitors🏒 Exhibitors & sponsors
πŸ† GamificationπŸ† Gamification console
πŸ’° BudgetπŸ’° Budget & break-even
πŸ“ˆ ReportsπŸ“Š Reports & analytics

On the hub page itself:

Three stat tilesPaid orders, revenue and ticket type count β€” the quick pulse check.
✨ Setup assistantDescribe promo codes, pricing windows, add-ons and registration questions in plain English and it builds them. See 🎟️ Ticketing & registration.
πŸŽ₯ Provision Zoom sessions Β· 🎀 Sync webinar panelistsπŸŽ₯ Zoom, recordings & the video library
πŸͺͺ Badge templateπŸ›‚ Onsite
πŸ’¬ Chat roomsπŸ’¬ Surveys, chat rooms & moderation
πŸ“’ Send announcement (push + banner)βœ‰οΈ Email, SMS & push
Orders🎟️ Ticketing β€” approvals and refunds
Ticket types🎟️ Ticketing β€” caps, invites and the waitlist

πŸ—ΊοΈ A sensible build order

  1. Create or clone the event and get the dates, slug and timezone right.
  2. Finish ticketing β€” pricing windows, promo codes, add-ons and your registration questions, via the ✨ setup assistant. β†’
  3. Build the agenda, then provision Zoom for the online sessions. β†’
  4. Bring in speakers and exhibitors, assign tasks, and send out booth portal links. β†’
  5. Publish, then start promoting β€” campaigns, drip emails and social. β†’
  6. Switch on the fun β€” gamification, surveys and chat rooms. β†’
  7. Prepare for the doors: badges, scanners, and the reminder to exhibitors about rep scan links. β†’
  8. Afterwards: reports, the post-event survey, and reconciling the budget. β†’